Why and how are you using this project?

[danielpza]

Hello everyone, I'd like to understand why are you using this project and if you are still using it for new projects.

TypeScript transformers plugins seems to be very niche and this plugin in particular has a few alternatives that seems to be more popular/up to date/better maintained/standard:

• Node.js subpath imports: built-in in Node.js, no compilation steps needed. Supported by typescript.
• yarn link protocol
• vite-tsconfig-paths
• webpack-tsconfig-paths
• tsconfig-paths
• rolldown seems to support tsconfig paths out of the box. tsdown would support it as well

It seems a waste to keep maintaining this project, but people keep using it/raising issues despite the alternatives.

Please let me know if you have an use case for this project, and if you have tried any other alternatives that couldn't solve your issue.

[zuozp8]

setting up Node.js subpath imports is a bit tricky, I needed to have .js suffix only on the right size in the package.js imports config

  "imports": {
    "#root/*": "./dist/src/*.js"
   }

[lppedd]

Saw this post only now. We're using it in a 100+ packages Nx monorepo driven by tsconfig path aliases, when compiling with tsc.
We prefer doing this because it avoids bundling: shorter feedback loop, tsc watches and recompiles only what's necessary, and we get better source map support in the various IDEs that get used.

[lppedd]

Note that I recommend this library to everyone in our situation. It has practically no bugs, and it works out-of-the-box with Nx.

[ChandlerFerry]

+1 using it for the same reason as lppedd. NX monorepo, driven by tsconfig path aliases.

This project has been the best way to avoid bundling internal libraries on a monorepo.

Will look into NodeJs Subpath imports.