All geek questions in one place

VSCode 0.3 cannot find 'node' runtime in path

I just updated from 0.1 vscode to 0.3. Now I get an error when starting the debugger "cannot find runtime" node "on path". I have iojs v2.3.0 working on OSX 10.10.3. I installed iojs using nvm, so it is possible that node is not in the path, but I can type "node" in the terminal and get an answer.

+6
source share
3 answers

NODE WAY FOR VSCODE 0.7.0 VERSION

I am running Ubuntu GNU / Linux 12.04.5 LTS. Before VSCode 0.7.0, I would leave my default node path found in PATH in the launch.json file:

// Workspace relative or absolute path to the runtime executable to be used. Default is the runtime executable on the PATH. "runtimeExecutable": null,

However, after upgrading to 0.7.0, I started getting errors 'can't find runtime on "node" PATH' , although node was on my PATH.

 18:25:37 ツgjsmith3rd@DV7 :~ $echo $PATH /usr/bin:...//Plus the rest of the PATH 18:25:44 ツgjsmith3rd@DV7 :~ 18:21:36 ツgjsmith3rd@DV7 :~ $which node /usr/bin/node 18:21:43 ツgjsmith3rd@DV7 :~

I changed my .json run to:

 // Workspace relative or absolute path to the runtime executable to be used. Default is the runtime executable on the PATH. "runtimeExecutable": "/user/bin/node",

Now everything is working fine. The actual path is /usr/bin/ , and the executable is node .

+6
source

This should not be related to updating VSCode. Reinstalling node should fix the problem or explicitly add your node runtime to PATH.

0
source

To resolve this problem, restart the computer. This will probably be allowed. I have a similar problem, my problem was solved by rebooting the operating system. fooobar.com/questions/989818 / ...

0
source

Source: https://habr.com/ru/post/989816/

More articles:


All Articles