-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
[JavaScript/Node.js] Support for "Go to definition" of code located in "node_modules" #2550
Comments
That's a bug. We will soon ship with a revamped JS language support and such things should be fixed then |
Nice, I'm looking forward to the next release 😄 |
Just checking, this still seems to be broken in the latest Insider build. Is that expected behaviour? It's a React Native Javascript project, if that matters :) |
Subscribed to this too. The feature could be very useful. |
@waderyan This is an issue with the typescript brain |
@jrieken just to make sure I understand, when you say "typescript brain" you mean the TypeScript language service, correct? |
yes |
This issue was moved to microsoft/TypeScript#10808 |
Moving to next milestone, as this cannot be verified at the moment |
Related to #26633 and I think it still not resolves yet. |
@nguyennb9 Me too. Got the same issue with fresh install of Vscode. E.g I'm using Angular 4 and Bulma. Can go to definition of Angular but but it can't go to others. Kind of strange. |
I am using "npm link ../../lib/my-lib" to symlink a local module that is shared across several apps into the "node_modules" directory of each of the apps. This is nice for developing the shared lib in combination with all the apps.
VS-Code does not allow me to navigate to this shared libraries' code by pressing F12 or "Go to definition". The same applies for all other npm modules inside the node_modules directory.
Is this restricted functionality intentional ? or should it be working and I am running to a JS parsing bug that prevents the "Go to definition" to do its work ?
If the "Go to definition" feature is not supposed to work for all things "node_modules" ... could we integrate an exception for symlink directories inside node_modules ?
Thanks
The text was updated successfully, but these errors were encountered: