Cannot find runtime 'node' on PATH. in Visual Studio Code running installed on Ubuntu 18.04
I want to debug my Node.Js code in visual studio code. when I add break point and starts debugging it gives me error "Cannot find runtime 'node' on PATH". I am runnimg VS Code in ubuntu 18.04. Can some help me in fixing this issue?
Any help in this regard will be highly appreciated.
visual-studio-code
asked Aug 14 '18 at 12:21
Programmer-XProgrammer-X
1337
add a comment |
I want to debug my Node.Js code in visual studio code. when I add break point and starts debugging it gives me error "Cannot find runtime 'node' on PATH". I am runnimg VS Code in ubuntu 18.04. Can some help me in fixing this issue?
Any help in this regard will be highly appreciated.
visual-studio-code
asked Aug 14 '18 at 12:21
Programmer-XProgrammer-X
1337
Yes, Node is installed. As, when I run command node -v in bash, it gives v10.7.0
– Programmer-X
Aug 14 '18 at 12:56
add a comment |
I want to debug my Node.Js code in visual studio code. when I add break point and starts debugging it gives me error "Cannot find runtime 'node' on PATH". I am runnimg VS Code in ubuntu 18.04. Can some help me in fixing this issue?
Any help in this regard will be highly appreciated.
visual-studio-code
asked Aug 14 '18 at 12:21
Programmer-XProgrammer-X
1337
I want to debug my Node.Js code in visual studio code. when I add break point and starts debugging it gives me error "Cannot find runtime 'node' on PATH". I am runnimg VS Code in ubuntu 18.04. Can some help me in fixing this issue?
Any help in this regard will be highly appreciated.
visual-studio-code
visual-studio-code
asked Aug 14 '18 at 12:21
Programmer-XProgrammer-X
1337
asked Aug 14 '18 at 12:21
Programmer-XProgrammer-X
1337
asked Aug 14 '18 at 12:21
Programmer-XProgrammer-X
1337
asked Aug 14 '18 at 12:21
Programmer-XProgrammer-X
1337
asked Aug 14 '18 at 12:21
Programmer-XProgrammer-X
1337
1337
Yes, Node is installed. As, when I run command node -v in bash, it gives v10.7.0
– Programmer-X
Aug 14 '18 at 12:56
add a comment |
Yes, Node is installed. As, when I run command node -v in bash, it gives v10.7.0
– Programmer-X
Aug 14 '18 at 12:56
Yes, Node is installed. As, when I run command node -v in bash, it gives v10.7.0
– Programmer-X
Aug 14 '18 at 12:56
Yes, Node is installed. As, when I run command node -v in bash, it gives v10.7.0
– Programmer-X
Aug 14 '18 at 12:56
add a comment |
2 Answers
2
active
oldest
votes
After alot of searching I resolved this issue myself by following these two steps:
- I opened the Integrated terminal and type command
which node. In my case it responded with/home/user/.nvm/versions/node/v10.7.0/bin/node
- Then I added an attribute "runtimeExecutable" in launch.json file and to its value I passed the path received by entering command mentioned in step one. like this
"runtimeExecutable": "/home/user/.nvm/versions/node/v10.7.0/bin/node",
Screenshot of launch.json file after adding "runtimeExecutable" in configurations
After following these two steps, I added break point and started debugging. It started debugging.
answered Aug 14 '18 at 15:10
Programmer-XProgrammer-X
1337
add a comment |
I had a similar issue with zsh and nvm on ubuntu 18.10, I fixed it by adding nvm initialization script in ~/.profile and restart login session like this
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion"
answered Mar 19 at 11:00
salamaashoushsalamaashoush
12
add a comment |
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1065276%2fcannot-find-runtime-node-on-path-in-visual-studio-code-running-installed-on-u%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
After alot of searching I resolved this issue myself by following these two steps:
- I opened the Integrated terminal and type command
which node. In my case it responded with/home/user/.nvm/versions/node/v10.7.0/bin/node
- Then I added an attribute "runtimeExecutable" in launch.json file and to its value I passed the path received by entering command mentioned in step one. like this
"runtimeExecutable": "/home/user/.nvm/versions/node/v10.7.0/bin/node",
Screenshot of launch.json file after adding "runtimeExecutable" in configurations
After following these two steps, I added break point and started debugging. It started debugging.
answered Aug 14 '18 at 15:10
Programmer-XProgrammer-X
1337
add a comment |
After alot of searching I resolved this issue myself by following these two steps:
- I opened the Integrated terminal and type command
which node. In my case it responded with/home/user/.nvm/versions/node/v10.7.0/bin/node
- Then I added an attribute "runtimeExecutable" in launch.json file and to its value I passed the path received by entering command mentioned in step one. like this
"runtimeExecutable": "/home/user/.nvm/versions/node/v10.7.0/bin/node",
Screenshot of launch.json file after adding "runtimeExecutable" in configurations
After following these two steps, I added break point and started debugging. It started debugging.
answered Aug 14 '18 at 15:10
Programmer-XProgrammer-X
1337
add a comment |
After alot of searching I resolved this issue myself by following these two steps:
- I opened the Integrated terminal and type command
which node. In my case it responded with/home/user/.nvm/versions/node/v10.7.0/bin/node
- Then I added an attribute "runtimeExecutable" in launch.json file and to its value I passed the path received by entering command mentioned in step one. like this
"runtimeExecutable": "/home/user/.nvm/versions/node/v10.7.0/bin/node",
Screenshot of launch.json file after adding "runtimeExecutable" in configurations
After following these two steps, I added break point and started debugging. It started debugging.
answered Aug 14 '18 at 15:10
Programmer-XProgrammer-X
1337
After alot of searching I resolved this issue myself by following these two steps:
- I opened the Integrated terminal and type command
which node. In my case it responded with/home/user/.nvm/versions/node/v10.7.0/bin/node
- Then I added an attribute "runtimeExecutable" in launch.json file and to its value I passed the path received by entering command mentioned in step one. like this
"runtimeExecutable": "/home/user/.nvm/versions/node/v10.7.0/bin/node",
Screenshot of launch.json file after adding "runtimeExecutable" in configurations
After following these two steps, I added break point and started debugging. It started debugging.
answered Aug 14 '18 at 15:10
Programmer-XProgrammer-X
1337
edited Aug 14 '18 at 15:42
answered Aug 14 '18 at 15:10
Programmer-XProgrammer-X
1337
answered Aug 14 '18 at 15:10
Programmer-XProgrammer-X
1337
answered Aug 14 '18 at 15:10
Programmer-XProgrammer-X
1337
1337
add a comment |
add a comment |
I had a similar issue with zsh and nvm on ubuntu 18.10, I fixed it by adding nvm initialization script in ~/.profile and restart login session like this
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion"
answered Mar 19 at 11:00
salamaashoushsalamaashoush
12
add a comment |
I had a similar issue with zsh and nvm on ubuntu 18.10, I fixed it by adding nvm initialization script in ~/.profile and restart login session like this
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion"
answered Mar 19 at 11:00
salamaashoushsalamaashoush
12
add a comment |
I had a similar issue with zsh and nvm on ubuntu 18.10, I fixed it by adding nvm initialization script in ~/.profile and restart login session like this
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion"
answered Mar 19 at 11:00
salamaashoushsalamaashoush
12
I had a similar issue with zsh and nvm on ubuntu 18.10, I fixed it by adding nvm initialization script in ~/.profile and restart login session like this
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion"
answered Mar 19 at 11:00
salamaashoushsalamaashoush
12
answered Mar 19 at 11:00
salamaashoushsalamaashoush
12
answered Mar 19 at 11:00
salamaashoushsalamaashoush
12
answered Mar 19 at 11:00
salamaashoushsalamaashoush
12
12
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1065276%2fcannot-find-runtime-node-on-path-in-visual-studio-code-running-installed-on-u%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Yes, Node is installed. As, when I run command node -v in bash, it gives v10.7.0
– Programmer-X
Aug 14 '18 at 12:56