npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@ayaseaki/swc-plugin-monorepo-relative-path-resolve

v0.1.2

Published

Resolve relative paths from source code of sub-packages in a monorepo.

Downloads

72

Readme

@ayaseaki/swc-plugin-monorepo-relative-path-resolve

A SWC plugin to handle resolving relative import paths like @/* and @common/* of sub-packages in a monorepo.

Why

For monorepo scene, we often have the need to directly import the source code of sub-packages to get a better bundle speed.

However, when a sub-package in a monorepo has its own path alias defined in its tsconfig.json, the bundle of base app may not respect the alias config, which results in a failure of resolution:

// sub-package/src/index.ts
import { foo } from '@/common/constants';
export { foo };

// sub-package/src/common/constants.ts
export const foo = 'foo';
// base/index.ts
import { foo } from 'sub-package'; 
console.log(foo);

// while compiling base/index.ts `Can't resolve @/common/constants` will be thrown

This plugin aims to resolve a subset of this issue: if your alias is just a relative of src path, you can use this swc plugin to dynamically replace the import alias during compile-time.

Usage

pnpm i -D @ayaseaki/swc-plugin-monorepo-relative-path-resolve

This plugin can handle the import source matching {prefix}{subpath}?/. For example:

  • @/*
  • @common/*
  • ~common/*

Usage with rspack:

// in rspack.config.js (ts):
{
  test: /\.(jsx?|tsx?)$/,
  use: [
    {
      loader: "builtin:swc-loader",
      options: {
        jsc: {
          // ...
          // add the following config:
          experimental: {
            plugins: [
              [
                "@ayaseaki/swc-plugin-monorepo-relative-path-resolve",
                {
                  prefix: "@",
                  allowedPathnames: ["common"],
                },
              ],
            ],
          },
        },
      },
    },
  ],
},

See example for detail.

Configration

prefix

  • type: string
  • description: specify the import prefix of your code.
  • default: @

allowedPathnames

  • type: string[]
  • description: specify the allowed pathnames after prefix, for example if you have a relative path @common/ and @components/, then you set allowedPathnames to ['common', 'components'.]
  • default: []