IMPORTANT: DO NOT USE! Use import mapping instead

A similar feature to this library is already available in node as a standard: import mapping.

Not only does it allow for directory mapping, but it also allows dependency aliasing, and works for both require and import (ESM) WITHOUT breaking resolution behaviour in production or other libraries like using this library does.

You have been warned.

I know this sounds hateful, however, that is not my intention. My intention is instead to spread awareness about this mostly undocumented feature (it is not shown in any package manifest documentation besides node’s, and it is relatively tucked away) so people can write better software without needing to use hacky libraries like this one and without adding unnecessary dependencies.

[Nytelife26]

@Papooch you will have to convert to using #alias instead of @alias, but that’s it.

"imports": {
    "#root/*": "./*",
    "#submodules/*": "./submodules/*",
    "#db/*": "./src/db/*",
    "#middleware/*": "./src/middleware/*"
}

I hope that helps.

[Kehrlann]

@Nytelife26 , thanks for raising awareness. This was introduced “recently”, so on older versions of node, you might still want module-alias - therefore we probably won’t just “deprecate” the package.

Would you mind opening a PR to update the README of this package, explaining that import mapping exists and should be used instead?