tsconfig-paths VS alias-hq

If you've use a re-map path in your project, you have to pass it up to tsconfig-paths like this,

There are multiple libraries available for configuring path aliases in Node.js, such as alias-hq and tsconfig-paths. However, while looking through the Node.js documentation, I discovered a way to configure path aliases without having to rely on third-party libraries. Moreover, this approach enables the use of aliases without requiring the build step.

If you're not using webpack, you can give tsconfig-paths a try.

Path mapping Very handy tsconfig-paths library allows to import modules from the filesystem without prefixing them with "./".

was just dealing with this yesterday. You need to use this package: https://github.com/dividab/tsconfig-paths

There are multiple libraries available for configuring path aliases in Node.js, such as alias-hq and tsconfig-paths. However, while looking through the Node.js documentation, I discovered a way to configure path aliases without having to rely on third-party libraries. Moreover, this approach enables the use of aliases without requiring the build step.

You could make it work by yourself, but… instead of spending some time figuring out how to do it (feel free to do it if you want or have time for that), I recommend you to check this amazing package (Alias HQ) which is free and basically uses your tsconfig.json or jsconfig.json file to setup everything for you and make really easy to configure all those more advanced needs.

Where I personally gave up on trying to use Yarn + PnP for my team's project was folder aliases. We had a few aliases set up using https://github.com/davestewart/alias-hq , so that we could use the same aliases with Node, Jest, and Webpack. That wouldn't work as-is, because again Yarn has to have full control over all package file access, and so it needs to understand what those aliases are. I got stuck trying to figure out how to get those aliases configured with Yarn instead, and gave up on PnP at that point.