module-alias icon indicating copy to clipboard operation
module-alias copied to clipboard

Register aliases of directories and custom module paths in Node

Results 58 module-alias issues
Sort by recently updated
recently updated
newest added

Hey @ilearnio, I've just released a package called Alias HQ: - https://github.com/davestewart/alias-hq/ It's an end-to-end solution for configuring, refactoring, maintaining and using path aliases. Was doing some research on how...

## Change Added a method that will take a alias as a string, validate that it exists in the moduleAliase's object. and that it is of type string. This will...

Say I have a directory that I want to resolve with module-alias. The directory doesn't have any js modules inside so I can't just do require.resolve("@storage/public"), I simply want to...

Allow module-alias to be initialized from multiple places, including separate packages in node_modules and nested/child packages (within source folder). It should add aliases to some global stack that will be...

Added new keys as discussed in the issue. The config object is loaded from ``` { module-alias: { aliases: {}, moduleDirectories: [] } } ``` Supports the old syntax too...

Yesterday I had need of aliases having multiple targets. It's somewhat complicated, but generally involves `pkg` and needing the ability to override certain files that are archived in the produced...

Hi guys, If we need to add support to Idea IDE I found the easiest way is creating webpack.config.js (even if you do not use it) with: ```JS const path...

When importing a component with a module alias import inside, mocha cannot find the module.

when trying to install with, it is added in package.json "module-alias": "^2.2.2", However if I run server, it is not found.

I am getting an issue when using `module-alias` with some private npm scoped packages. For example, given we have defined `_moduleAliases` configuration in `package.json`, it works well without any private...