Skip to content

Cannot lookup for the global linked node_modules #20401

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

Closed
mjbvz opened this issue Dec 1, 2017 · 5 comments
Closed

Cannot lookup for the global linked node_modules #20401

mjbvz opened this issue Dec 1, 2017 · 5 comments
Labels
Duplicate An existing issue was already created

Comments

@mjbvz
Copy link
Contributor

mjbvz commented Dec 1, 2017

From @nguyennb9 on May 15, 2017 5:25

  • VSCode Version: Code 1.12.1 (f6868fce3eeb16663840eb82123369dec6077a9b, 2017-05-04T21:18:32.269Z)
  • OS Version: Darwin x64 16.5.0
  • Extensions:
Extension Author Version
beautify HookyQR 1.0.2
project-manager alefragnani 0.16.0
theme-desertex casualjim 0.0.6
vscode-svgviewer cssho 1.4.0
vscode-eslint dbaeumer 1.2.8
githistory donjayamanne 0.2.0
json-tools eriklynd 1.0.2
prettier-vscode esbenp 0.17.1
flow-for-vscode flowtype 0.6.0
vscode-icon-theme jtlowe 1.5.0
Go lukehoban 0.6.61
addDocComments stevencl 0.0.8
react-beautify taichi 0.3.0

In my project, I create a lib module and linked it to the global module by command npm link: (https://docs.npmjs.com/cli/link). But in the editor, I cannot navigate to that module.

Steps to Reproduce:

  1. Create a node module name my_lib, make it global by npm link
    Extra step is to check if it work correctly by npm -g ls | grep my_lib
  2. In your code, import that lib:
    const my_lib = require('my_lib');
  3. Try to using the inner function, CMD + click, find the function... VSCode cannot navigate to the linked folder.

Copied from original issue: microsoft/vscode#26633

@mjbvz mjbvz self-assigned this Dec 1, 2017
@mjbvz mjbvz added Bug A bug in TypeScript javascript labels Dec 1, 2017
@mjbvz
Copy link
Contributor Author

mjbvz commented Dec 1, 2017

From @nguyennb9 on June 8, 2017 5:24

How was this issue so far?

@mjbvz
Copy link
Contributor Author

mjbvz commented Dec 1, 2017

From @nguyennb9 on September 7, 2017 1:36

Well, how can I do this manually?

@mjbvz
Copy link
Contributor Author

mjbvz commented Dec 1, 2017

Moving over to TS. I gave this a quick try but also wasn't able to get a npm linked module to be picked up by intellisense

@mhegazy
Copy link
Contributor

mhegazy commented Dec 2, 2017

Duplicate of #8760

@mhegazy mhegazy marked this as a duplicate of #8760 Dec 2, 2017
@mhegazy mhegazy added the Duplicate An existing issue was already created label Dec 2, 2017
@typescript-bot
Copy link
Collaborator

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Duplicate An existing issue was already created
Projects
None yet
Development

No branches or pull requests

3 participants