ilearnio / module-alias Public
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "module-alias" to package.json #50
Comments
|
@ilearnio, I'm taking this issue. Can I? There is an alternative way too, instead of using the package.json file. We can use ".module-alias-rc" or something similar like ".babelrc" and ".prettierrc". Thoughts? |
|
@mfaheemakhtar Sure. That would be great!
I said this earlier but now I think it would be more clear if the properties would be called |
|
Would also be nice to be able to define for different environments in this config {
"development": {
"aliases": [...]
},
// ...
} |
|
_moduleAliases, _moduleDirectories and any other option starting with underscore is ignored in auto-generated package.json (in app.asar) by electron-builder. I think it is better to use module-alias option, or any options that is not starting with underscore, instead of _moduleAliases. Related issue: Auto generated package.json does not contain settings starting with undersore |
Right now we have
_moduleAliasesand_moduleDirectoriesoptions that we read from package.json. It makes sense to move them into"module-alias": { alias, modules }(namesalias, modulescan be different, just took them from WebPack https://webpack.js.org/configuration/resolve/)The text was updated successfully, but these errors were encountered: