blocks|key|1901373|text|解决方案是设置别名default。在操作系统终端运行-|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1901374|nvm+alias+default+7.8.0|1901375|打开vscode，现在运行node+-v返回7.8.0|1901376|vscode似乎使用这个(别名默认值)值，而不是nvm+use+X.X.X设置的节点版本。|1901377|重新启动VS代码以获取更改。|1901378|entityMap^0|9|7|0|0|N|0|D|7|M|5|0|O|D|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|13|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|O|$]]

The solution is to set alias <code>default</code>. In the OS terminal run -
<code>nvm alias default 7.8.0</code>
Open vscode, now running <code>node -v</code> returns <code>7.8.0</code>
It seems vscode takes up this (alias default) value and not the node version that is set by <code>nvm use X.X.X</code>
Restart VS code for it to pick up the changes.

blocks|key|1901880|text|在VS代码中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1901881|转到您的launch.json文件|unordered-list-item|offset|length|style|CODE|1901882|在配置中添加runtimeVersion属性，如下所示|1901883|在本例中，我们假设4.8.7已经使用nvm安装：|BOLD|1901884|{
"version":+"<some-version>",
"configurations":+[
++++{
++++++++"type":+"node",
++++++++"runtimeVersion":+"4.8.7",+//+If+i+need+to+run+node+4.8.7
++++++++"request":+"launch",
++++++++"name":+"Launch",
++++++++"program":+"${workspaceFolder}/sample.js"
++++}
]}|code-block|syntax|javascript|1901885|entityMap^0|0|4|B|0|6|E|0|9|5|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@$E|W|F|X|G|H]]|9|@]|A|$]]|$1|I|3|J|5|D|7|Y|8|@$E|Z|F|10|G|H]]|9|@]|A|$]]|$1|K|3|L|5|6|7|11|8|@$E|12|F|13|G|M]]|9|@]|A|$]]|$1|N|3|O|5|P|7|14|8|@]|9|@]|A|$Q|R]]|$1|S|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|T|$]]

In VS Code:
<ul>
<li>go to your <code>launch.json</code> file</li>
<li>add the <code>runtimeVersion</code> attribute inside configurations as shown below</li>
</ul>
In this example, we are assuming 4.8.7 is already installed using nvm:
<pre><code>{
&quot;version&quot;: &quot;&lt;some-version&gt;&quot;,
&quot;configurations&quot;: [
 {
 &quot;type&quot;: &quot;node&quot;,
 &quot;runtimeVersion&quot;: &quot;4.8.7&quot;, // If i need to run node 4.8.7
 &quot;request&quot;: &quot;launch&quot;,
 &quot;name&quot;: &quot;Launch&quot;,
 &quot;program&quot;: &quot;${workspaceFolder}/sample.js&quot;
 }
]}
</code></pre>

blocks|key|602983|text|将runtimeExecutable添加到.vscode/launch.json中，如下所示|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|602984|{
++"type":+"node",
++"request":+"launch",
++"name":+"App",
++"program":+"${workspaceRoot}/index.js",
++"runtimeExecutable":+"${env:HOME}/.nvm/versions/node/v6.9.2/bin/node"
}|code-block|syntax|javascript|602985|entityMap^0|1|H|L|J|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

add <code>runtimeExecutable</code> to your <code>.vscode/launch.json</code> like this

<pre><code>{
 "type": "node",
 "request": "launch",
 "name": "App",
 "program": "${workspaceRoot}/index.js",
 "runtimeExecutable": "${env:HOME}/.nvm/versions/node/v6.9.2/bin/node"
}
</code></pre>

blocks|key|1901839|text|我也有同样的问题，无法在我的OS环境中，不仅用VSCode，而且用Atom编辑器(使用platformio-ide终端包来管理集成的终端)，将我的节点版本通过nvm保存在我的OS环境中。除了我没有使用调试器，而是在特定的任务中使用吞咽和咕哝之外，以前的答案中没有一个对我有用。显然，nvm与集成的终端或子shell不太协调，至少在这些编辑器中是这样的，因为在加载它们时，环境变量$PATH会在内部进行修改，并根据此包的贡献者之一在本文中报告的注释进行以下操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1901840|“@charsleysa我知道nvm抛出此错误的原因，在您的子subshell中，路径的/usr/local/bin:/bin:/usr/sbin:/sbin部分已经从路径的末尾移动到开始。|blockquote|1901841|当nvm启动时，它会调用nvm_change_path+(我的贡献将它从nvm_prepend_path更改为此)，这将修改nvm--路径的相关部分。|unordered-list-item|1901842|然后，通过询问npm是什么，Nvm检查当前npm前缀。由于/usr/local/bin/npm现在具有优先地位，它报告/usr/local/bin。|1901843|然后，Nvm检查npm报告的当前前缀是否位于当前nvm节点版本的目录树中(在此阶段，默认nvm别名解析到的节点版本的安装目录)。|1901844|前缀不是该树的一部分，因此它会关闭自身(在进程中调用nvm_strip_path，这就是为什么您的子subshell的路径中没有与nvm相关的路径)，并将得到的错误抛出。macOS的/etc/profile+(或/etc/zprofile)调用/usr/libexec/+PATH+_helper，它执行路径切换。|1901845|在父shell中，路径中还没有nvm+dir，所以当nvm运行时，它会将其目录添加到路径中。但是在子subshell中，PATH已经被macOS重新配置，将任何非系统目录放在最后，我们就有了问题。“|1901846|在启动任何一个集成终端时，我总是收到这样的消息：|1901847|nvm与npm配置“前缀”选项不兼容:当前设置为"/usr/local“运行npm+config+delete+prefix或nvm+use+--delete-prefix+vx.x.x+--silent来取消它。|offset|length|style|CODE|1901848|在我的案例中，我为解决这一问题所做的是报告的同一问题的“变通”部分，实质上是：|1901849|通过在我的~/..bash_profile中添加以下行来重置路径:+PATH="/usr/local/bin:$(getconf+)“|1901850|在此之后，当我在两个编辑器上启动任何集成终端时，不要再发出警告，我可以与nvm交互，以便在任何节点版本之间轻松切换，而且完全没有问题。|1901851|这是另一个的另一种选择，以防这个没有多大帮助。|1901852|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/Microsoft/vscode/issues/37296^0|0|0|0|0|0|0|0|0|12|O|1R|13|0|0|0|0|2|3|0|0^^$0|@$1|2|3|4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1E|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|1F|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|1G|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|1H|8|@]|9|@]|A|$]]|$1|L|3|M|5|G|7|1I|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1J|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1K|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1L|8|@$T|1M|U|1N|V|W]|$T|1O|U|1P|V|W]]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|Z|3|10|5|G|7|1R|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|1S|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|1T|8|@]|9|@$T|1U|U|1V|1|1W]]|A|$]]|$1|15|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]]|16|$17|$5|18|19|1A|A|$1B|1C]]]]

I had the same problem of being unable to keep my node version specified trough nvm in my OS X environment not only with VSCode but also with Atom Editor (using the platformio-ide-terminal package for managing the integrated terminal in it). None of the suggestions in the previous answers worked for me, besides me not using the debugger but using gulp and grunt for specific tasks. Apparently nvm does not get along with the integrated terminals or sub shells at least in these editors because when loading them the environment variable $PATH is modified internally and does the following according to a comment by one of the contributors of this package in this issue reported here <a href="https://github.com/creationix/nvm/issues/1652" rel="noreferrer">NVM fails to load within nested shell #1652</a>:

<blockquote>
 " @charsleysa I know why nvm is throwing this error. In your subshell, somehow the /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin part of your PATH has been moved from the end of the PATH to the start.
 
 <ul>
 <li>When nvm is then started, it calls nvm_change_path (my contribution changed it to this from nvm_prepend_path), which modifies the nvm-relevant part of the path in place.</li>
 <li>Nvm then checks the current npm prefix by asking npm what it is. Since /usr/local/bin/npm now has precendence, it reports /usr/local/bin.</li>
 <li>Nvm then checks whether the current prefix as reported by npm is in the directory tree of the current nvm node version (at this stage, the installation directory of the node version your default nvm alias resolves to).</li>
 <li>The prefix is not part of that tree, so it deactivates itself (calling nvm_strip_path in the process, which is why there's no nvm-related path in your subshell's PATH), and bails with the error you're getting.
 macOS's /etc/profile (or /etc/zprofile) calls /usr/libexec/path_helper, which does the PATH switcheroo.</li>
 </ul>
 
 In the parent shell, the PATH doesn't yet have an nvm dir in it, so by the time nvm runs, it prepends its directory to the path. But in the subshell, PATH has been reconfigured by macOS to put any non-system directories at the end and we have the problem."
</blockquote>

I was always getting this message when launching any integrated terminal:

nvm is not compatible with the npm config "prefix" option: currently set to "/usr/local"
Run <code>npm config delete prefix</code> or <code>nvm use --delete-prefix vx.x.x --silent</code> to unset it.

What I did to solve this in my case was the "workaround" part of that same issue reported which is essentially the following:

<ul>
<li>Reset the path by adding the following line inside my ~/.bash_profile at the very top before anything else:
PATH="/usr/local/bin:$(getconf PATH)"</li>
</ul>

And after that no more warnings when I launch any integrated terminal on both editors and I can interact with nvm to switch between any node version easily and without problems at all.

Here it is <a href="https://github.com/Microsoft/vscode/issues/37296" rel="noreferrer">another</a> alternative just in case this one doesn`t help that much.

blocks|key|604052|text|所提供的一些答案是正确的和被支持的，但有些不完整。这个程序对我有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|604053|打开终端窗口+run++VS+Code并运行node+-v。例如，您将得到v10.12.0。|ordered-list-item|offset|length|style|BOLD|CODE|604054|打开终端窗口在+VS+Code之外，用nvm更改节点版本(即。nvm+use+v12.14.0)|604055|Cmd%2B+Shift+%2B+p并选择Preferences+>+Open+(JSON)|604056|将"terminal.integrated.shellArgs.osx":+[]添加到用户配置中|604057|Cmd%2B+Shift+%2B+p并选择Shell命令:在PATH中安装'code‘命令|604058|关闭和代码。|604059|打开终端窗口并运行code。这将使用一个新的和更新的/+zsh会话打开bash与代码。|604060|打开终端窗口+run++VS+Code并运行node+-v。你会得到v12.14.0的。|604061|奖励:如果您总是希望在VS代码的终端上获得特定的节点版本，请将其设置为默认，方法是在+VS+Code之外打开终端窗口并运行：|604062|nvm+alias+default+v12.14.0|code-block|syntax|javascript|604063|entityMap^0|0|6|5|C|7|M|7|11|8|0|6|1|8|7|J|3|O|2|V|G|0|0|3|5|5|D|1|H|P|0|1|13|0|0|3|5|5|D|1|H|D|0|2|3|0|9|4|S|3|Z|4|Q|G|0|6|5|C|7|M|7|Y|8|0|0|16|17|7|1M|4|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|17|8|@$E|18|F|19|G|H]|$E|1A|F|1B|G|H]|$E|1C|F|1D|G|I]|$E|1E|F|1F|G|I]]|9|@]|A|$]]|$1|J|3|K|5|D|7|1G|8|@$E|1H|F|1I|G|H]|$E|1J|F|1K|G|H]|$E|1L|F|1M|G|H]|$E|1N|F|1O|G|H]|$E|1P|F|1Q|G|I]]|9|@]|A|$]]|$1|L|3|M|5|D|7|1R|8|@$E|1S|F|1T|G|I]|$E|1U|F|1V|G|I]|$E|1W|F|1X|G|I]|$E|1Y|F|1Z|G|H]]|9|@]|A|$]]|$1|N|3|O|5|D|7|20|8|@$E|21|F|22|G|I]]|9|@]|A|$]]|$1|P|3|Q|5|D|7|23|8|@$E|24|F|25|G|I]|$E|26|F|27|G|I]|$E|28|F|29|G|I]|$E|2A|F|2B|G|H]]|9|@]|A|$]]|$1|R|3|S|5|D|7|2C|8|@$E|2D|F|2E|G|H]]|9|@]|A|$]]|$1|T|3|U|5|D|7|2F|8|@$E|2G|F|2H|G|I]|$E|2I|F|2J|G|I]|$E|2K|F|2L|G|I]|$E|2M|F|2N|G|H]]|9|@]|A|$]]|$1|V|3|W|5|D|7|2O|8|@$E|2P|F|2Q|G|H]|$E|2R|F|2S|G|H]|$E|2T|F|2U|G|I]|$E|2V|F|2W|G|I]]|9|@]|A|$]]|$1|X|3|Y|5|6|7|2X|8|@$E|2Y|F|2Z|G|H]|$E|30|F|31|G|H]|$E|32|F|33|G|H]]|9|@]|A|$]]|$1|Z|3|10|5|11|7|34|8|@]|9|@]|A|$12|13]]|$1|14|3|-4|5|6|7|35|8|@]|9|@]|A|$]]]|15|$]]

Some of the answers provided are correct and upvoted, but somewhat incomplete. This procedure worked for me:

<ol>
<li>Open the terminal window inside VS Code and run <code>node -v</code>. You'll get for instance <code>v10.12.0</code>.</li>
<li>Open a terminal window outside VS Code Change your node version with nvm (ie. <code>nvm use v12.14.0</code>)</li>
<li><code>Cmd</code>+ <code>Shift</code> + <code>p</code> and choose Preferences > Open Settings (JSON)</li>
<li>Add <code>"terminal.integrated.shellArgs.osx": []</code> to your user config</li>
<li><code>Cmd</code>+ <code>Shift</code> + <code>p</code> and choose Shell Command: Install 'code' command in PATH</li>
<li>Close VS Code.</li>
<li>Open a terminal window and run <code>code</code>. This will open VS Code with a new and updated <code>bash</code> / <code>zsh</code> session.</li>
<li>Open the terminal window inside VS Code and run <code>node -v</code>. You'll get <code>v12.14.0</code>.</li>
</ol>

Bonus: If you always want to get a particular node version on VS Code's terminal, set it as default by opening a terminal window outside VS Code and running:

<pre class="lang-sh prettyprint-override"><code>nvm alias default v12.14.0
</code></pre>

blocks|key|1944973|text|我使用的是噢-my，它也没有使用nvm指定的节点版本。尝试了一些在这里发布的建议，但我解决这个问题的唯一方法是在~/.zshrc顶部添加以下行|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1944974|PATH="/usr/local/bin:$(getconf+PATH)"|code-block|syntax|javascript|1944975|entityMap^0|1K|8|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

I am using oh-my-zsh and it too was not using the node version specified by nvm. Tried several suggestions posted here, but the only way I managed to resolve this issue was by adding the following line to the top of <code>~/.zshrc</code>

<pre><code>PATH="/usr/local/bin:$(getconf PATH)"
</code></pre>

blocks|key|1944868|text|我也有同样的问题，但上面的答案没有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1944869|显然，在我使用shellArgs时，osx的默认bash设置为bash。我通过将用户设置中的shellArgs设置为空数组解决了这个问题：|offset|length|style|CODE|1944870|"terminal.integrated.shellArgs.osx":+[]|1944871|entityMap^0|0|7|9|O|4|V|4|1A|9|0|0|13|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]|$D|R|E|S|F|G]|$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$]]

I had the same problem, but the above answers didn't help.

Apparently the default <code>shellArgs</code> for osx are set to <code>bash</code> while I'm using <code>zsh</code>. I solved the problem by setting the <code>shellArgs</code> in my user settings to an empty array:

<code>"terminal.integrated.shellArgs.osx": []</code>

blocks|key|603209|text|我发现的另一种解决方案是，在使用nvm选择节点之后，从shell中简单地启动代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|603210|您需要首先打开命令托盘，并选择“安装‘代码’到路径”。|603211|​|603212|📷|atomic|offset|length|603213|603214|然后启动终端，通过nvm选择节点，然后启动“代码”。|603215|603216|603217|603218|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/82f6f27f4ef8cd361aae669ff2b68199.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/41ffc1118b8270c40198e4ca1e26207c.png^0|0|0|0|0|1|0|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|14|8|@]|9|@$I|15|J|16|1|17]]|A|$]]|$1|K|3|E|5|6|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|19|8|@]|9|@]|A|$]]|$1|N|3|E|5|6|7|1A|8|@]|9|@]|A|$]]|$1|O|3|G|5|H|7|1B|8|@]|9|@$I|1C|J|1D|1|1E]]|A|$]]|$1|P|3|E|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X|Y|-4]]|Z|$5|T|U|V|A|$W|10|Y|-4]]]]

A alternative solution I've found is to simply launch code from the shell after you pick your node using nvm.

You need to first open the command pallet and select "install 'code' into 
path".

<a href="https://i.stack.imgur.com/ryxlm.png" rel="noreferrer"><img src="https://i.stack.imgur.com/ryxlm.png" alt="enter image description here"></a>

And then launch a terminal and select your node via nvm and then launch "code".

<a href="https://i.stack.imgur.com/Qhh7s.png" rel="noreferrer"><img src="https://i.stack.imgur.com/Qhh7s.png" alt="enter image description here"></a>

blocks|key|1945163|text|我也遇到了同样的问题，我发现了一个奇怪的解决办法，可能会对未来的其他人有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1945164|如果我不设置eslint.runtime，那么我的系统正在为eslint服务器运行节点v10.11.0，而我希望它运行的是已安装并通过nvm默认的v12.13.0。|offset|length|style|CODE|1945165|我发现v10版本的节点是由brew根据@franziga的答案安装的，但是我想要的节点版本是由nvm安装的。因此，我通过brew卸载v10.11.0并关闭/重新打开VS代码。奇怪的是，埃斯林特还在报道它是开始使用v10的。|1945166|我试着在任何启动脚本中运行一个没有更改我的PATH的shell，并且节点的版本仍然按预期正确地指向v12，但是VS代码仍然为eslint启动v10。|1945167|我不知道如何检查由eslint运行的可执行文件的路径，如果我打开一个集成的终端，所有操作都可以与预期版本的节点(v12)很好地配合。|1945168|解决办法(对我而言)：|1945169|我发现，如果在"eslint.runtime":+"node"中设置settings.json，它现在将使用在终端上使用code+.打开vscode时活动的任何版本的node。只有"node"+-没有路。|1945170|entityMap^0|0|6|E|17|8|1V|3|21|8|0|D|4|1B|3|1U|8|0|L|4|0|0|0|7|O|Y|D|1O|6|2B|4|2I|6|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@$D|V|E|W|F|G]|$D|X|E|Y|F|G]|$D|Z|E|10|F|G]|$D|11|E|12|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|13|8|@$D|14|E|15|F|G]|$D|16|E|17|F|G]|$D|18|E|19|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1A|8|@$D|1B|E|1C|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1D|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1E|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1F|8|@$D|1G|E|1H|F|G]|$D|1I|E|1J|F|G]|$D|1K|E|1L|F|G]|$D|1M|E|1N|F|G]|$D|1O|E|1P|F|G]]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|S|$]]

I had this same issue and I found a strange workaround that may be helpful to someone else in the future.

If I do not set <code>eslint.runtime</code> my system was running node <code>v10.11.0</code> for eslint server, whereas I wanted it to be running <code>v12.13.0</code> which I had installed and made default via <code>nvm</code>.

I found that the v10 version of node was installed by <code>brew</code> based on @franziga's answer but my desired version of node was installed by <code>nvm</code>. So, I uninstalled <code>v10.11.0</code> via brew and closed/reopened VS Code. Strangely, eslint was still reporting that it was started using v10.

I tried running a shell without any changes to my <code>PATH</code> in any startup scripts, and the version of node was still correctly pointed to v12 as expected, but VS code still starts up v10 for eslint.

I'm not sure how to check the path of the executable that is being run by eslint, and if I open an integrated terminal everything works fine with the expected version of node (v12).

<h2>Solution (for me):</h2>

I found that if I set <code>"eslint.runtime": "node"</code> in <code>settings.json</code> that it will now use whatever version of <code>node</code> was active when I opened vscode using <code>code .</code> on the terminal. Just <code>"node"</code> - no path.

blocks|key|1945488|text|这里有很多复杂的答案。在我的例子中，这是由以前安装过的节点造成的。通过删除以下目录来修正它：rm+-rf+/usr/local/bin/npm和rm+-rf+/usr/local/bin/node，然后在VSC中运行nvm+use+default来获取由nvm安装的节点版本。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1945489|entityMap^0|1A|P|20|Q|30|F|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

Lots of complicated answers here. In my case, this was caused by node having previously having been installed. Fixed it by deleting the following directories: <code>rm -rf /usr/local/bin/npm</code> and <code>rm -rf /usr/local/bin/node</code>, then running <code>nvm use default</code> in VSC to pick up the node version installed by nvm.

blocks|key|1945135|text|尤其是对于shell，我没有任何问题，但您可以：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1945136|检查您的shell是否正确配置或改变它+(您可能对vscode或终端使用不同的shell)|unordered-list-item|offset|length|1945137|检查您的env，如果没有正确设置，请使用terminal.integrated.env.|style|CODE|1945138|我对vscode本身有问题，没有任何解决方案可以帮助我。因此，我使用了下面的启动脚本。|1945139|++++{
++++++++"type":+"node",
++++++++"request":+"launch",
++++++++"name":+"Launch+Program",
++++++++"program":+"${workspaceFolder}/server.js",
++++++++"runtimeExecutable":+"/bin/bash",
++++++++"runtimeArgs":+["-c",+".+~/.nvm/nvm.sh;nvm+run+default+\"$@\"",+"dummy"]
++++},|code-block|syntax|javascript|1945140|这假设您已经将其配置为bash+(否则将其更改为您的shell)，并且您希望使用nvm配置的default节点版本(您也可以更改它)。|1945141|备注：需要“虚拟”参数，以便正确解析其余参数。|BOLD|1945142|对“虚拟”的一个更长的解释:+Shell脚本使用位置参数，其中第一个参数将是脚本位置本身(由$0处理)，当使用-c标志时，脚本将在没有设置$0的情况下被读取。vscode将传递一些参数，例如节点开始脚本位置，这将被错误地解释，因此“虚拟”推送所有参数的一个点。它可以是任何东西，但它必须在那里。|1945143|entityMap|0|LINK|mutability|MUTABLE|url|https://code.visualstudio.com/docs/editor/integrated-terminal|1|https://code.visualstudio.com/updates/v1_15#_configure-environment-of-terminal-sessions^0|0|G|3|0|0|K|O|K|O|1|0|0|0|1A|7|0|0|2|0|1A|2|1J|2|1X|2|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|19|8|@]|9|@$E|1A|F|1B|1|1C]]|A|$]]|$1|G|3|H|5|D|7|1D|8|@$E|1E|F|1F|I|J]]|9|@$E|1G|F|1H|1|1I]]|A|$]]|$1|K|3|L|5|6|7|1J|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|1K|8|@]|9|@]|A|$P|Q]]|$1|R|3|S|5|6|7|1L|8|@$E|1M|F|1N|I|J]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1O|8|@$E|1P|F|1Q|I|V]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1R|8|@$E|1S|F|1T|I|J]|$E|1U|F|1V|I|J]|$E|1W|F|1X|I|J]]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]|16|$5|11|12|13|A|$14|17]]]]

Particularly with the shell I had no problems, but you may:

<ul>
<li>check your shell is properly configure or <a href="https://code.visualstudio.com/docs/editor/integrated-terminal" rel="noreferrer">change it</a> (you might be using different shells for vscode or your terminal)</li>
<li>check your env and if it's not properly set use the <a href="https://code.visualstudio.com/updates/v1_15#_configure-environment-of-terminal-sessions" rel="noreferrer"><code>terminal.integrated.env.&lt;platform&gt;</code></a></li>
</ul>

I had issues with vscode itself and no solution could help me. So I finished using the following launch script.

<pre><code> {
 "type": "node",
 "request": "launch",
 "name": "Launch Program",
 "program": "${workspaceFolder}/server.js",
 "runtimeExecutable": "/bin/bash",
 "runtimeArgs": ["-c", ". ~/.nvm/nvm.sh;nvm run default \"$@\"", "dummy"]
 },
</code></pre>

this assumes you have it configure for bash (otherwise change it to your shell) and you want to use the <code>default</code> node version as configured by nvm (you may also change it).

Note: The "dummy" parameter is required so the rest of the parameters are properly parsed. 

A longer explanation of "dummy": Shell scripts use positional parameters where the first one will be the script location itself (addressed by <code>$0</code>), when using the <code>-c</code> flag the script is read inplace an there is no <code>$0</code> being set. vscode will pass some arguments, like the node start script location which will be wrongly interpreted, so "dummy" pushes all parameters one spot. It can be just anything, but it must be there.

blocks|key|1902590|text|我发现在调用代码之前在子shell中本地设置节点版本很好，而不更改当前shell中的版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1902591|$+(nvm+use+14;+code+.)|code-block|syntax|javascript|1902592|因此，要使它对任何项目文件夹透明地工作，请在项目文件夹中创建一个文件.precode，其中包含要在启动代码之前生成的shell命令--例如，|offset|length|style|CODE|1902593|nvm+use+14|1902594|然后添加到~/.bashrc中|1902595|pre_code(){
++++if+[+$#+==+1+]+&&++[+-f+${1}/.precode+]+;+then
++++++++echo+"(source+${1}/.precode+;++`which+code`+${@})"
++++++++(source+${1}/.precode+;+`which+code`+${@})
++++else
++++++++`which+code`+${@}
++++fi
}+++
alias+code='pre_code'|1902596|(注意:在编辑之前打开的任何shell中运行source+~/.bashrc，以便编辑生效。)|1902597|然后，假设存在必要的文件~/myproject/.precode，将代码从|1902598|$+code+~/myproject|1902599|将导致对shell的一些诊断输出。|1902600|source+github/myproject/.precode
Now+using+node+v14.15.1+(npm+v6.14.8)|1902601|同时，在终端窗口和调试器中启动一个具有正确节点版本的新vscode窗口。然而，在启动它的外壳中，原始节点版本仍然存在。|1902602|$+node+-v
v12.19.1|1902603|entityMap^0|0|0|Y|8|0|0|5|9|0|0|M|G|0|C|K|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1A|8|@$I|1B|J|1C|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|1D|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|1E|8|@$I|1F|J|1G|K|L]]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1H|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|1I|8|@$I|1J|J|1K|K|L]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1L|8|@$I|1M|J|1N|K|L]]|9|@]|A|$]]|$1|W|3|X|5|D|7|1O|8|@]|9|@]|A|$E|F]]|$1|Y|3|Z|5|6|7|1P|8|@]|9|@]|A|$]]|$1|10|3|11|5|D|7|1Q|8|@]|9|@]|A|$E|F]]|$1|12|3|13|5|6|7|1R|8|@]|9|@]|A|$]]|$1|14|3|15|5|D|7|1S|8|@]|9|@]|A|$E|F]]|$1|16|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]]|17|$]]

I found that setting the node version locally in a sub shell before calling code works well, while not changing the version in the current shell, e.g.
<pre><code>$ (nvm use 14; code .)
</code></pre>
Therefore, to make it work transparently for any project folder, create a file <code>.precode</code> in the project folder with shell commands to source before starting code - e.g.,
<pre><code>nvm use 14
</code></pre>
Then add to <code>~/.bashrc</code>
<pre class="lang-sh prettyprint-override"><code>pre_code(){
 if [ $# == 1 ] &amp;&amp; [ -f ${1}/.precode ] ; then
 echo &quot;(source ${1}/.precode ; `which code` ${@})&quot;
 (source ${1}/.precode ; `which code` ${@})
 else
 `which code` ${@}
 fi
} 
alias code='pre_code'
</code></pre>
(Note: Run <code>source ~/.bashrc</code> in any shell opened before the edit in order for the edit to take effect.)
Then, assuming the necessary file <code>~/myproject/.precode</code> exists, starting code with
<pre><code>$ code ~/myproject
</code></pre>
will result in some diagnostic output on the shell, e.g.
<pre><code>source github/myproject/.precode
Now using node v14.15.1 (npm v6.14.8)
</code></pre>
as well launching a new vscode window with the correct node version in the terminal window and debugger. However, in the shell from which it was launched, the original node version remains, e.g.
<pre class="lang-sh prettyprint-override"><code>$ node -v
v12.19.1
</code></pre>

blocks|key|604438|text|在关闭VS代码的所有实例后，设置默认别名只对我有效。简单地重新加载窗口是行不通的。nvm+ls将正确显示默认别名集，但在VS代码第一次打开时(跨所有窗口)将继续使用版本集。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|604439|还有一个问题，就是在repos中有多个节点版本，这正是nvm真正要解决的问题。最后，我将以下内容添加到我的.zshrc文件的底部：|604440|++[+-s+"./.nvmrc"+]+&&+nvm+use|code-block|syntax|javascript|604441|本质上，当一个新的shell启动时，它会检查当前目录中是否存在一个非空的.nvmrc，如果存在，则使用该版本。如果没有安装该版本，您将收到一条这样的消息。运行nvm+install后，应该在所有新的终端会话中正确加载。|604442|正如自述文件所指出的，您还可以使用nvm+自述文件中显示的目录更改的自动版本切换。虽然项目终端通常总是在与您的.nvmrc文件相同的目录中打开，所以这个解决方案比较简单，只在终端启动时运行。|604443|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/nvm-sh/nvm#zsh|1^0|15|6|0|1H|6|0|0|10|6|27|B|0|1J|6|2|4|0|L|4|1|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|15|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@$9|1E|A|1F|1|1G]|$9|1H|A|1I|1|1J]]|E|$]]|$1|Q|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]|Y|$5|T|U|V|E|$W|X]]]]

Setting the default alias only worked for me after closing all instances of VS Code. Simply reloading the window wouldn't work. <code>nvm ls</code> would show the default alias set correctly but would keep using the version set when VS code was first opened (across all windows).
There's also the issue of having multiple node versions across repos, which is really what nvm is meant to solve. In the end I added the following to the bottom of my <code>.zshrc</code> file:
<pre class="lang-sh prettyprint-override"><code> [ -s &quot;./.nvmrc&quot; ] &amp;&amp; nvm use
</code></pre>
Essentially when a new shell starts, it checks to see if a non-empty <code>.nvmrc</code> exists in the current directory and if so, uses that version. If that version is not installed you will get a message saying so. After running <code>nvm install</code> it should load properly in all new terminal sessions.
You can also use the automatic version switching on directory changes shown in the nvm <a href="https://github.com/nvm-sh/nvm#zsh" rel="noreferrer">README</a> as <a href="https://stackoverflow.com/users/14954327/asiera">@asiera</a> pointed out. Although a project terminal will typically always open in the same directory as your <code>.nvmrc</code> file, so this solution is a bit simpler and only runs on terminal startup.

blocks|key|1944888|text|我尝试了所有建议的解决方案，但都没有效果。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1944889|/usr/local/bin/节点指向某个位置。我创建了一个指向特定nvm节点文件夹的符号链接，解决了这个问题：|1944890|ln+-s+/Users/mad/.nvm/versions/node/v11.1.0/bin/node+/usr/local/bin/node|code-block|syntax|javascript|1944891|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I tried all the suggested solutions but nothing was working.

/usr/local/bin/node was pointing to somewhere. i made a symlink to a specific nvm node folder and that was solving the issue for me:

<pre><code>ln -s /Users/mad/.nvm/versions/node/v11.1.0/bin/node /usr/local/bin/node
</code></pre>

blocks|key|1944900|text|我也遇到了同样的问题，我发现node是由brew和nvm安装的。我卸载了由brew安装的brew，现在终端和visual代码上的版本都是相同的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1944901|entityMap^0|E|4|K|4|P|3|11|4|18|4|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|G|$]]

I have the same problem and I found that I have <code>node</code> installed by <code>brew</code> and <code>nvm</code>. I uninstalled <code>node</code> installed by <code>brew</code> and the versions on both terminal and visual studio code are the same now.

blocks|key|604065|text|您不需要修改默认的节点版本。下面的示例假设节点6是默认版本，并且希望VSCode引用节点的版本7：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|604066|#+open+a+terminal+instance
nvm+use+7
code+.+#+or+project+folder+instead+of+"."
#+when+VSCode+start,+you+may+use+ctrl%2B`+to+open+the+integrated+terminal
#+then+check+the+node+version+in+the+integrated+terminal
node+-v+#+should+print+7|code-block|syntax|javascript|604067|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You don't need to modify your default node version. The following example assumes that node 6 is your default version and you want VSCode to reference version 7 of node:

<pre class="lang-sh prettyprint-override"><code># open a terminal instance
nvm use 7
code . # or project folder instead of "."
# when VSCode start, you may use ctrl+` to open the integrated terminal
# then check the node version in the integrated terminal
node -v # should print 7
</code></pre>

blocks|key|1902627|text|在阅读了这个线程并测试了几乎所有的建议之后，如果您正在使用nvm:在命令中添加nvm+use，我发现了一个非常简单的解决方案。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1902628|启动调试器需要更多的时间，但这对我来说是值得的，因为现在我不必每次开始处理不同的项目时都要执行nvm+use并在终端上打开Vscode。|1902629|这是我的.vscode/launch.json文件。祝好运!|1902630|{
++++//+Use+IntelliSense+to+learn+about+possible+attributes.
++++//+Hover+to+view+descriptions+of+existing+attributes.
++++//+For+more+information,+visit:+https://go.microsoft.com/fwlink/?linkid=830387
++++"version":+"0.2.0",
++++"configurations":+[
++++++++{
++++++++++++"command":+"nvm+use+&&+yarn+start",
++++++++++++"name":+"Launch",
++++++++++++"request":+"launch",
++++++++++++"type":+"node-terminal",
++++++++},
++++]
}|code-block|syntax|javascript|1902631|entityMap^0|13|7|0|1B|7|0|4|J|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|Z|8|@]|D|@]|E|$M|N]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

After reading this thread and testing almost all suggestions, I found a very simple solution if you are using nvm: Add <code>nvm use</code> in the command.
It's gonna take a little more time to start the debugger, but it is worth it to me because now I don't have to execute <code>nvm use</code> and open Vscode by the terminal every time I start working on a different project.
Here is my <code>.vscode/launch.json</code> file. Good luck!
<pre class="lang-js prettyprint-override"><code>{
 // Use IntelliSense to learn about possible attributes.
 // Hover to view descriptions of existing attributes.
 // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
 &quot;version&quot;: &quot;0.2.0&quot;,
 &quot;configurations&quot;: [
 {
 &quot;command&quot;: &quot;nvm use &amp;&amp; yarn start&quot;,
 &quot;name&quot;: &quot;Launch&quot;,
 &quot;request&quot;: &quot;launch&quot;,
 &quot;type&quot;: &quot;node-terminal&quot;,
 },
 ]
}
</code></pre>

blocks|key|604344|text|我希望解决方案是特定于工作区的，并且不需要我自己执行任何操作(每次启动终端时不需要重做nvm+use+<version>+)，我找到的解决方案：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|604345|在我的项目的根部创建.nvmrc文件，按nvm+ReadMe中的说明，旧的节点版本。|ordered-list-item|604346|在我的~/..zshrc中添加自动激活脚本，也在ReadMe中添加自动激活脚本(bashrc脚本也在自述文件中)|604347|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/nvm-sh/nvm#nvmrc|1|https://github.com/nvm-sh/nvm#zsh^0|17|H|0|A|6|O|6|0|0|O|6|1|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@$9|Y|A|Z|B|C]]|D|@$9|10|A|11|1|12]]|E|$]]|$1|I|3|J|5|H|7|13|8|@]|D|@$9|14|A|15|1|16]]|E|$]]|$1|K|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]|S|$5|N|O|P|E|$Q|T]]]]

I wanted the solution to be workspace specific and not requiring any action on my part (not having to redo <code>nvm use &lt;version&gt;</code> each time i start a terminal)
The solution I found:
<ol>
<li>create the <code>.nvmrc</code> file at the root of my project that old the node version I want to use as stated in nvm <a href="https://github.com/nvm-sh/nvm#nvmrc" rel="nofollow noreferrer">ReadMe</a></li>
<li>adding the automatic activation script in my ~/.zshrc also in the <a href="https://github.com/nvm-sh/nvm#zsh" rel="nofollow noreferrer">ReadMe</a> (bashrc script also in the readme)</li>
</ol>

blocks|key|1945296|text|那么，您的nvm配置得很好，但是其他版本的节点仍然继续接管吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1945297|删除节点的所有非nvm版本：|1945298|brew+uninstall+--force+node+(纱线在没有系统节点的情况下会很好)|ordered-list-item|offset|length|style|CODE|1945299|从pkg或其他非nvm方法安装的其他版本。|1945300|重新登录。现在，无论shell如何启动，都无法与nvm争夺路径。|1945301|注:安装/升级纱线时，使用brew+install+yarn+--without-node|1945302|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/11178106/1914507^0|0|0|0|R|0|0|L|0|0|0|D|W|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@$G|11|H|12|I|J]]|9|@]|A|$]]|$1|K|3|L|5|F|7|13|8|@]|9|@$G|14|H|15|1|16]]|A|$]]|$1|M|3|N|5|F|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@$G|19|H|1A|I|J]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

So, your nvm is configured well, but other version of node STILL keeps taking over?
Remove all non-nvm versions of node:
<ol>
<li><code>brew uninstall --force node</code> (yarn will be fine without system node)</li>
<li><a href="https://stackoverflow.com/a/11178106/1914507">Other version installed from pkg or other non-nvm method</a></li>
<li>Re-login. Now, nothing can be fighting for path with nvm no matter how is shell launched.</li>
</ol>
Note: When installing/upgrading yarn, use <code>brew install yarn --without-node</code>

blocks|key|1902688|text|VSCode+Shell+args似乎不受欢迎，这里使用VS代码的settings.json中的概要文件进行更新|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1902689|这消除了-l终端参数，将其转换为交互式shell与登录shell。|1902690|"terminal.integrated.profiles.osx":+{
++++"zsh+(normal+-+me)":+{
++++++++"path":+"zsh",
++++++++"args":+[]
++++}
},
"terminal.integrated.defaultProfile.osx":+"zsh+(normal+-+me)"|code-block|syntax|javascript|1902691|谢谢!答案这里表示解释，这里表示旧args方式：|1902692|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/50011895/400836|1|https://stackoverflow.com/a/53596328/400836^0|X|D|0|4|2|0|0|5|2|0|C|2|1|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|14|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|15|8|@]|D|@$9|16|A|17|1|18]|$9|19|A|1A|1|1B]]|E|$]]|$1|O|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]|W|$5|R|S|T|E|$U|X]]]]

VSCode Shell args seems to be deprecated, here's update using profiles in VS Code's <code>settings.json</code>:
This gets rid of the <code>-l</code> terminal argument turning it into an interactive shell vs a login shell.
<pre><code>&quot;terminal.integrated.profiles.osx&quot;: {
 &quot;zsh (normal - me)&quot;: {
 &quot;path&quot;: &quot;zsh&quot;,
 &quot;args&quot;: []
 }
},
&quot;terminal.integrated.defaultProfile.osx&quot;: &quot;zsh (normal - me)&quot;
</code></pre>
Thanks! the answers <a href="https://stackoverflow.com/a/50011895/400836">here</a> for explanation and <a href="https://stackoverflow.com/a/53596328/400836">here</a> for old args way:

blocks|key|604456|text|对我来说，我只是做了：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|604457|#+in+a+separate+terminal+(i.e+not+in+VScode+teminal)
nvm+install+<node+version>|code-block|syntax|javascript|604458|然后在VScode终端：|604459|nvm+use+<the+node+version+you+installed>|604460|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

For me I simply did:
<pre><code># in a separate terminal (i.e not in VScode teminal)
nvm install &lt;node version&gt;
</code></pre>
then in VScode terminal:
<pre><code>nvm use &lt;the node version you installed&gt;
</code></pre>

blocks|key|1902818|text|下面的解决方案对我有效|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1902819|首先，使用nvm安装并使用所需的节点版本，并使用以下命令：nvm+install+v16.13.1和nvm+use+v16.13.1。|ordered-list-item|offset|length|style|CODE|1902820|然后在Linux上使用which+node命令获取当前使用节点的路径名。它会像这样的/usr/local/nvm/versions/node/v16.13.1/bin/node|1902821|最后，在launch.json的runtimeExecutable选项中使用这个路径名。|1902822|launch.json文件|1902823|{
++++"version":+"0.2.0",
++++"configurations":+[
++++++++{+++
++++++++++++"type":+"pwa-node",
++++++-->+++"runtimeExecutable":+"/usr/local/nvm/versions/node/v16.13.1/bin/node",
++++++++++++"request":+"launch",
++++++++++++"args":+["testcode/hunter.js","127.0.0.1:9229"],
++++++++++++"name":+"Launch+Program",
++++++++++++"skipFiles":+[
++++++++++++++++"<node_internals>/**"
++++++++++++],
++++++++++++"program":+"${workspaceFolder}/index.js"
++++++++}
++++]
}|code-block|syntax|javascript|1902824|entityMap|0|LINK|mutability|MUTABLE|url|https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_launch-configuration-attributes^0|0|5|3|T|K|1E|G|0|B|A|16|1A|0|4|B|G|H|G|H|0|0|0|B|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|12|8|@$E|13|F|14|G|H]|$E|15|F|16|G|H]|$E|17|F|18|G|H]]|9|@]|A|$]]|$1|I|3|J|5|D|7|19|8|@$E|1A|F|1B|G|H]|$E|1C|F|1D|G|H]]|9|@]|A|$]]|$1|K|3|L|5|D|7|1E|8|@$E|1F|F|1G|G|H]|$E|1H|F|1I|G|H]]|9|@$E|1J|F|1K|1|1L]]|A|$]]|$1|M|3|N|5|6|7|1M|8|@$E|1N|F|1O|G|H]]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1P|8|@]|9|@]|A|$R|S]]|$1|T|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]]]

following solution worked for me
<ol>
<li>first install and use the desired node version with <code>nvm</code> with these commands: <code>nvm install v16.13.1</code> and <code>nvm use v16.13.1</code>.</li>
<li>then get the pathname of the currently using node with <code>which node</code> command on Linux.
it will be something like this <code>/usr/local/nvm/versions/node/v16.13.1/bin/node</code></li>
<li>finally use this pathname in <code>launch.json</code> for <a href="https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_launch-configuration-attributes" rel="nofollow noreferrer"><code>runtimeExecutable</code></a> option.</li>
</ol>
the <code>launch.json</code> file
<pre class="lang-json prettyprint-override"><code>{
 &quot;version&quot;: &quot;0.2.0&quot;,
 &quot;configurations&quot;: [
 { 
 &quot;type&quot;: &quot;pwa-node&quot;,
 --&gt; &quot;runtimeExecutable&quot;: &quot;/usr/local/nvm/versions/node/v16.13.1/bin/node&quot;,
 &quot;request&quot;: &quot;launch&quot;,
 &quot;args&quot;: [&quot;testcode/hunter.js&quot;,&quot;127.0.0.1:9229&quot;],
 &quot;name&quot;: &quot;Launch Program&quot;,
 &quot;skipFiles&quot;: [
 &quot;&lt;node_internals&gt;/**&quot;
 ],
 &quot;program&quot;: &quot;${workspaceFolder}/index.js&quot;
 }
 ]
}
</code></pre>

blocks|key|1945596|text|根据nvm的文档，您需要将此代码片段添加到您的~/.bashrc、~/.profile或~/.zshrc文件中，因此请打开该文件并粘贴到其中，重新启动vscode并享受nvm。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1945597|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"++#+This+loads+nvm+bash_completion|code-block|syntax|javascript|1945598|来源：https://github.com/nvm-sh/nvm#manual-install|1945599|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/nvm-sh/nvm#manual-install^0|N|9|X|A|18|8|0|0|3|18|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|M|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

According to the docs of nvm, you need to add this code snippet to your <code>~/.bashrc</code>, <code>~/.profile</code>, or <code>~/.zshrc</code> file, so open the file and paste this in, restart vscode and enjoy nvm
<pre><code>export NVM_DIR=&quot;$HOME/.nvm&quot;
[ -s &quot;$NVM_DIR/nvm.sh&quot; ] &amp;&amp; \. &quot;$NVM_DIR/nvm.sh&quot; # This loads nvm
[ -s &quot;$NVM_DIR/bash_completion&quot; ] &amp;&amp; \. &quot;$NVM_DIR/bash_completion&quot; # This loads nvm bash_completion
</code></pre>
source: <a href="https://github.com/nvm-sh/nvm#manual-install" rel="nofollow noreferrer">https://github.com/nvm-sh/nvm#manual-install</a>

blocks|key|1902289|text|没有尝试所有的解决方案，但对我来说，更新nvm只是起了作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1902290|只需遵循安装这里并确保您的bash_profile已被更新。|offset|length|style|CODE|1902291|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/nvm-sh/nvm#install--update-script^0|0|D|C|6|2|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]]|9|@$D|T|E|U|1|V]]|A|$]]|$1|H|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

Did not tried all of the solution, but for me updating nvm simply worked.

Just follow the installation <a href="https://github.com/nvm-sh/nvm#install--update-script" rel="nofollow noreferrer">here</a> and make sure that you <code>bash_profile</code> is updated.

blocks|key|1902568|text|其他的解决方案对我都没有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1902569|所以我运行了nvm+alias+default+node，它为我修复了它。|offset|length|style|CODE|1902570|entityMap^0|0|6|M|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

None of the other solutions worked for me.
So I ran <code>nvm alias default node</code> and this fixed it for me.

blocks|key|1945381|text|我在上面尝试了几种选择，但它们都没有用。我找到了一个简单的解决方案。在VS代码终端中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1945382|单击终端下拉菜单上的向下箭头。|ordered-list-item|1945383|选择默认外壳|1945384|选择“bash”|1945385|尝试node+-v并返回设置为默认nvm+alias+default+v12.14.0的正确版本|offset|length|style|CODE|1945386|entityMap^0|0|0|0|0|2|7|H|Q|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|S|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|T|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|U|8|@$K|V|L|W|M|N]|$K|X|L|Y|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|P|$]]

I tried several of the options here at the top and they didn't work. I found a simple solution. In the VS Code terminal:
<ol>
<li>Click the down arrow on the terminal dropdown</li>
<li>Select Default Shell</li>
<li>Select 'bash'</li>
<li>Try <code>node -v</code> and that should return the correct version that was set as default <code>nvm alias default v12.14.0</code></li>
</ol>

blocks|key|1902665|text|在MAC上检查默认的交互式shell。如果是zsh，那么将VS代码中的终端设置为zsh模式如何？然后，您可以在Mac上使用指定的节点版本。这对我有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1902666|我使用的是macOS+Big+v11.2.1+%2B+VS代码v1.55.1|unordered-list-item|1902667|设置象形|offset|length|1902668|entityMap|0|LINK|mutability|MUTABLE|url|https://i.stack.imgur.com/WuLYu.png^0|0|0|0|4|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|S|8|@]|9|@$G|T|H|U|1|V]]|A|$]]|$1|I|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

Check your default interactive shell on your MAC.
If it's zsh, how about setting the terminal in VS Code to zsh mode as well? Then you can use the specified node version on the Mac. This works for me.
<ul>
<li>I'm using macOS Big Sur v11.2.1 + VS Code v1.55.1</li>
</ul>
<a href="https://i.stack.imgur.com/WuLYu.png" rel="nofollow noreferrer">Setting pictrue</a>

blocks|key|1902694|text|sudo+rm+-rf+/usr/local/opt/node@<YOUR_NODE_VERSION>|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1902695|然后重新启动视觉代码|unstyled|1902696|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>sudo rm -rf /usr/local/opt/node@&lt;YOUR_NODE_VERSION&gt;
</code></pre>
then restart the Visual Code

blocks|key|1902728|text|如果使用nvm，则可能会得到以下结果：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1902729|在vscode中，setting.json更改类型记录键如下所示：|1902730|++"code-runner.executorMap":+{

++++//+"typescript":+"ts-node",
++++"typescript":+"node+-r+${NVM_BIN}/../lib/node_modules/ts-node/register",|code-block|syntax|javascript|1902731|如果这对你有用，那我来解释一下。|1902732|首先我试着把它|1902733|${NVM_BIN}/ts-node/register|offset|length|style|CODE|1902734|但那不管用。然后，我查看了目录中的内容，发现ts节点有一个符号链接：|1902735|ts-node+->+../lib/node_modules/ts-node/dist/bin.js|1902736|所以，我想这就是为什么普通的‘ts-节点/寄存器’不能正确解析的原因，因为它实际上变成了‘ts-node/dist/bin.js/寄存器’，这不应该工作。|1902737|希望这能帮上忙。|1902738|entityMap^0|0|0|0|0|0|0|R|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|16|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|17|8|@$O|18|P|19|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1A|8|@]|9|@]|A|$]]|$1|U|3|V|5|F|7|1B|8|@]|9|@]|A|$G|H]]|$1|W|3|X|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1D|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|11|$]]

If one uses nvm, then this may work out:
In vscode setting.json change typescript key like this:
<pre class="lang-json prettyprint-override"><code> &quot;code-runner.executorMap&quot;: {

 // &quot;typescript&quot;: &quot;ts-node&quot;,
 &quot;typescript&quot;: &quot;node -r ${NVM_BIN}/../lib/node_modules/ts-node/register&quot;,
</code></pre>
If it works for you, then here is my explanation.
First I tried to just put it
<code>${NVM_BIN}/ts-node/register</code>
but that didn't work. Then I looked inside the directory and found out that ts-node there is a symlink:
<pre class="lang-sh prettyprint-override"><code>ts-node -&gt; ../lib/node_modules/ts-node/dist/bin.js
</code></pre>
So, I guess that is why plain 'ts-node/register' is not resolving properly, because it actualy becomes 'ts-node/dist/bin.js/register' which shouldn't work.
Hope that might help someone.

blocks|key|1902833|text|如果这些答案对你都没有用，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1902834|如果您以前已经通过下载和解压缩来安装节点。去usr/local/lib，就会有一个叫nodejs的家伙坐在那里。|offset|length|style|CODE|1902835|把他踢出去。|1902836|并再次将nvm+alias+default设置为首选版本。就是这样，从此就幸福了。不过至少为我工作过。|1902837|entityMap^0|0|M|D|0|0|4|H|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

If none of this answers worked for you,
If you have previously installed node by downloading and unzipping it.
Go to <code>usr/local/lib</code> and there will be this guy sitting around named nodejs.
Kick him out.
And set <code>nvm alias default</code> to preferred version again.
That's it, happily ever after. At least worked for me though.

blocks|key|1945839|text|如果您想为您的Visual脚本运行程序设置Node版本，下面是每个项目的工作方式。因此，无需就必须设置全局nvm默认值。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|1945840|"NPM脚本运行程序“指的是直接在package.json中的悬停和执行脚本功能。|1945841|​|1945842|📷|atomic|1945843|1945844|分步|1945845|将包含项目节点版本的.nvmrc文件放置到项目的根文件夹中。|ordered-list-item|1945846|启用自动环境，如下所述：https://github.com/nvm-sh/nvm#deeper-shell-integration。|1945847|打开VS代码的settings.json并定义您喜欢的shell+(在我的例子中，它是zsh)。对于自动化配置文件，重要的是定义一个登录和交互式+shell+(参数-l和-i)：|1945848|++++"terminal.integrated.automationProfile.osx":+{
++++++++"path":+"/bin/zsh",
++++++++"icon":+"play",
++++++++"args":+["-l",+"-i"],
++++},
++++"terminal.integrated.profiles.osx":+{
++++++++"bash":+null,
++++++++"zsh":+{
++++++++++++"path":+"/bin/zsh",
++++++++++++"icon":+"star",
++++++++}
++++},|code-block|syntax|javascript|1945849|结果|1945850|打开一个新的shell会触发NVM+(图标显示哪个设置正在工作)：|1945851|1945852|1945853|1945854|运行NPM脚本会触发NVM：|1945855|1945856|1945857|1945858|1945859|1945860|1945861|干杯!|1945862|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/34b1beffd5ee287602093d8a02a0b908.png|imageAlt|1|LINK|MUTABLE|url|https://github.com/nvm-sh/nvm#deeper-shell-integration|2|https://developer.qcloudimg.com/http-save/yehe-900000/921f10bfaf8ef99f18ae2044b2260397.png|3|https://developer.qcloudimg.com/http-save/yehe-900000/b0bbaff48faabe73d2049fd885edd954.png|4|https://developer.qcloudimg.com/http-save/yehe-900000/6de108616155c0ad87d9e4fd5c8a84ea.png^0|7|C|18|2|1H|3|0|H|C|0|0|0|1|0|0|0|0|A|6|0|C|1I|1|0|7|D|17|3|2A|2|2D|2|1U|2|1X|3|0|0|0|0|0|0|1|2|0|0|0|0|0|1|3|0|0|0|0|1|4|0|0|0^^$0|@$1|2|3|4|5|6|7|23|8|@$9|24|A|25|B|C]|$9|26|A|27|B|C]|$9|28|A|29|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|2A|8|@$9|2B|A|2C|B|D]]|E|@]|F|$]]|$1|I|3|J|5|6|7|2D|8|@]|E|@]|F|$]]|$1|K|3|L|5|M|7|2E|8|@]|E|@$9|2F|A|2G|1|2H]]|F|$]]|$1|N|3|J|5|6|7|2I|8|@]|E|@]|F|$]]|$1|O|3|P|5|6|7|2J|8|@]|E|@]|F|$]]|$1|Q|3|R|5|S|7|2K|8|@$9|2L|A|2M|B|D]]|E|@]|F|$]]|$1|T|3|U|5|S|7|2N|8|@]|E|@$9|2O|A|2P|1|2Q]]|F|$]]|$1|V|3|W|5|S|7|2R|8|@$9|2S|A|2T|B|D]|$9|2U|A|2V|B|D]|$9|2W|A|2X|B|D]|$9|2Y|A|2Z|B|D]|$9|30|A|31|B|C]|$9|32|A|33|B|C]]|E|@]|F|$]]|$1|X|3|Y|5|Z|7|34|8|@]|E|@]|F|$10|11]]|$1|12|3|13|5|6|7|35|8|@]|E|@]|F|$]]|$1|14|3|15|5|6|7|36|8|@]|E|@]|F|$]]|$1|16|3|J|5|6|7|37|8|@]|E|@]|F|$]]|$1|17|3|L|5|M|7|38|8|@]|E|@$9|39|A|3A|1|3B]]|F|$]]|$1|18|3|J|5|6|7|3C|8|@]|E|@]|F|$]]|$1|19|3|1A|5|6|7|3D|8|@]|E|@]|F|$]]|$1|1B|3|J|5|6|7|3E|8|@]|E|@]|F|$]]|$1|1C|3|L|5|M|7|3F|8|@]|E|@$9|3G|A|3H|1|3I]]|F|$]]|$1|1D|3|J|5|6|7|3J|8|@]|E|@]|F|$]]|$1|1E|3|J|5|6|7|3K|8|@]|E|@]|F|$]]|$1|1F|3|L|5|M|7|3L|8|@]|E|@$9|3M|A|3N|1|3O]]|F|$]]|$1|1G|3|J|5|6|7|3P|8|@]|E|@]|F|$]]|$1|1H|3|1I|5|6|7|3Q|8|@]|E|@]|F|$]]|$1|1J|3|-4|5|6|7|3R|8|@]|E|@]|F|$]]]|1K|$1L|$5|1M|1N|1O|F|$1P|1Q|1R|-4]]|1S|$5|1T|1N|1U|F|$1V|1W]]|1X|$5|1M|1N|1O|F|$1P|1Y|1R|-4]]|1Z|$5|1M|1N|1O|F|$1P|20|1R|-4]]|21|$5|1M|1N|1O|F|$1P|22|1R|-4]]]]

In case you'd like to set the Node version for your Visual Studio Code NPM script runner, here's what works on a per-project basis. So, without having to set global <code>nvm</code> defaults.
By &quot;NPM script runner&quot; I mean the hover-and-execute-scripts functionality directly in <code>package.json</code>:
<a href="https://i.stack.imgur.com/jsXbB.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/jsXbB.png" alt="Visual Studio Code NPM script runner" /></a>
<h2>Step-by-step</h2>
<ol>
<li>Place an <code>.nvmrc</code> file containing the project's Node version into the root folder of your project.
</li>
<li>Enable automatic environment as described here: <a href="https://github.com/nvm-sh/nvm#deeper-shell-integration" rel="nofollow noreferrer">https://github.com/nvm-sh/nvm#deeper-shell-integration</a>.
</li>
<li>Open VS Code's <code>settings.json</code> and define your preferred shell (in my case, it's <code>zsh</code>). For the automation profile, it's important to define a login and interactive shell (arguments <code>-l</code> and <code>-i</code>):
</li>
</ol>
<pre class="lang-json prettyprint-override"><code> &quot;terminal.integrated.automationProfile.osx&quot;: {
 &quot;path&quot;: &quot;/bin/zsh&quot;,
 &quot;icon&quot;: &quot;play&quot;,
 &quot;args&quot;: [&quot;-l&quot;, &quot;-i&quot;],
 },
 &quot;terminal.integrated.profiles.osx&quot;: {
 &quot;bash&quot;: null,
 &quot;zsh&quot;: {
 &quot;path&quot;: &quot;/bin/zsh&quot;,
 &quot;icon&quot;: &quot;star&quot;,
 }
 },
</code></pre>
<h2>Result</h2>
Opening a new shell triggers NVM (The icons show which setting is working):
<a href="https://i.stack.imgur.com/uDqvm.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/uDqvm.png" alt="enter image description here" /></a>
And running an NPM script triggers NVM:
<a href="https://i.stack.imgur.com/5Uk1U.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/5Uk1U.png" alt="enter image description here" /></a>
<a href="https://i.stack.imgur.com/lzS5V.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/lzS5V.png" alt="enter image description here" /></a>
Cheers!

blocks|key|1903402|text|我需要vs代码来了解节点版本，而不是终端。从终端开始code是一种选择，但是如果你忘记了.|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1903403|一个更灵活的方法是在开始vs代码之前使用automator来创建您需要的环境。|1903404|运行Automator并启动一个新的应用程序项目。只需添加一个shell脚本(在实用程序下)，并添加以下行来创建"normal“(login%2Binteractive)+shell，您可以在其中启动代码：|1903405|zsh+-lic+code|code-block|syntax|javascript|1903406|如下所示：|1903407|📷|atomic|1903408|​|1903409|将其保存在应用程序文件夹中，名为“您每次查找vs代码时都会找到它”(我要么键入vs，要么输入代码，所以我称之为"vs代码运行程序“)|1903410|这里的好处是，您也可以应用其他配置。想法是一样的：|1903411|设置环境|ordered-list-item|1903412|星码|1903413|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/a32414604bed9cb3706a0d145f3eb540.png|imageAlt^0|Q|4|0|0|2|9|0|0|0|0|1|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1D|8|@$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1G|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1H|8|@$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|1K|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1L|8|@]|D|@]|E|$]]|$1|Q|3|R|5|S|7|1M|8|@]|D|@$9|1N|A|1O|1|1P]]|E|$]]|$1|T|3|U|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|1R|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|1S|8|@]|D|@]|E|$]]|$1|Z|3|10|5|11|7|1T|8|@]|D|@]|E|$]]|$1|12|3|13|5|11|7|1U|8|@]|D|@]|E|$]]|$1|14|3|-4|5|6|7|1V|8|@]|D|@]|E|$]]]|15|$16|$5|17|18|19|E|$1A|1B|1C|-4]]]]

I needed to vs code to be aware of the node version, not the terminal. Starting <code>code</code> from a terminal is an option, but if you forget...
A much more flexible way is to use automator to create the environment you need before starting vs code.
Run <code>Automator</code> and start a new Application project. Just add a Shell-Script (under Utilities) and add the following line to create a &quot;normal&quot; (login+interactive) shell, where you may start code:
<pre class="lang-bash prettyprint-override"><code>zsh -lic code

</code></pre>
This is how it looks like:
<a href="https://i.stack.imgur.com/r3Qvr.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/r3Qvr.png" alt="automator-shell script" /></a>
Save it in your Application folder with a name you'l find it every time you look for vs code (I either type vs or code, so I called it &quot;vs code runner&quot;)
The bonus here is that you can apply other configurations too. the idea is the same:
<ol>
<li>setup the environment</li>
<li>starat code</li>
</ol>

Is it possible for VS Code to use node version specified by NVM? 

I have 6.9.2 installed locally. Even after switching to another version, from the OS X terminal (not the VS Code terminal), restarting VS Code, VS Code still shows using 6.9.2.

OS X terminal

<pre><code>MacBook-Pro-3:~ mac$ node -v
v7.8.0
</code></pre>

VS Code Terminal

<pre><code>MacBook-Pro-3:QB-Invoice-API mac$ node -v
v6.9.2
</code></pre>

Visual Studio Code to use node version specified by NVM

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

VS代码是否可以使用NVM指定的节点版本？我在本地安装了6.9.2。即使切换到另一个版本，从OS终端(而不是VS代码终端)，重新启动VS代码，VS代码仍然显示使用6.9.2。OS X终端MacBook-Pro-3:~ mac$ node -vv7.8.0与代码终端MacBook-Pro-3:QB-Invoice-API mac$ node -vv6.9.2

问Visual代码使用NVM指定的节点版本
EN

回答 32

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Visual代码使用NVM指定的节点版本EN

回答 32

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Visual代码使用NVM指定的节点版本
EN