-
Notifications
You must be signed in to change notification settings - Fork 69
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
A way for VSCode to detect the location of the aliased directory #128
Comments
You need to create a file inside of the root project, called
Did you already try this one? |
Wow! you got it! Thank you |
Thank you, it was a life saver 🙏 |
Hello to everyone, If I may, using this config in This is my "_moduleAliases": {
"@": "build/src"
} To fix intellisense in
My vscode config file looks like this: {
"path-intellisense.mappings": {
"@": "${workspaceRoot}/src"
},
} You can refer to this repository for a complete example Best reguards |
It did not work for me in Nodejs(18.13.0) Project. Could you please look at this?
package.json
jsconfig.json
|
ensure that require('module-alias/register') is run prior to calling any alias directory otherwise you will get error |
Using the normal require function gives the developers benefit of hovering over the function then VSCode will be able to show the necessary arguments of the function. Moreover, you can click
alt
to go directly to the hovered function. Is there a way to do this using this library?An image using the normal require function
Requiring a module using
module-alias
The text was updated successfully, but these errors were encountered: