-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
Cannot find runtime 'node' on PATH. #10876
Comments
@UVk could you please launch the 'integrated terminal' in VS Code and run |
Im getting this issue now as well. and node is in the proper location. Im on the Insiders program.
|
@wprater could you please launch the 'integrated terminal' in VS Code and run |
Getting this issue as well.
Mac OSX 10.11.5 Doing a |
Same issue on Linux Ubuntu using nvm. |
same issue with VS Code 1.10.2 on MacOS Sierra
|
@sebsto @devmao @weinand I think the problem is that VS Code doesn't load a fresh environment (eg. run ~/.bash_profile) for each instance of VS Code. Even when you close all instances of VS Code it will use a cached environment unless you right-click->quit the application. If you have changed the node version using a manager such as NVM you need to do either of the following:
I would say this is a bug as you would expect VS Code to reload the environment every time you launch a new window. Note: I think this only applies to MacOS |
VS Code does the right thing. It reads the environment from |
@joaomoreno Yes is does the right thing (read .bashrc) but wrongly only does this once at startup and not for every new window? |
Got it. Duplicate of #15452 |
@joaomoreno I don't believe ticket #15452 covers this issue. Ticket #15452 explicitly accepts the current behaviour and states "that [new] window will inherit the current process env (which is normal OS X behaviour)". Although this is not normal behaviour; when you open a new tab on any terminal program you get a fresh environment. |
Note that Code isn't a terminal program. But sure: created an issue for this #23649 |
I am using nvm and I fixed the issue by adding
to to find nvm node executable path run |
Above solution work for me. |
Steps to Reproduce:
Cannot debug node application. Reinstalled node and VS, added node to PATH. nothing worked.
The text was updated successfully, but these errors were encountered: