blocks|key|2885513|text|Windows+(或者linux)上的环境变量似乎存在问题。它确实在OS上工作。我们正在调查。希望很快就能解决问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2885514|更新(2015年6月2日)：VisualStudioCode0.3.0包含对此的修复。|offset|length|style|BOLD|2885515|entityMap^0|0|0|E|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|$]]

There seems to be a problem with environment variables on Windows (and probably on linux). It does work on OS X. We are investigating. Expect a fix soon.

Update (June 2, 2015): Visual Studio Code 0.3.0 contains a fix for this.

blocks|key|2885591|text|作为一种解决方法，您可以在启动VSCode时设置环境变量，例如，使用下面这个简短的powershell脚本：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2885592|param(
+$vars+=+@{}
)

$vars.Keys+%7C+%25+{
++++write-host+"adding+env+variable:+$_=$($vars[$_])"
++++[Environment]::SetEnvironmentVariable($_,+$vars[$_],+"Process")
}
$ver+=+"0.1.0"
&+"$env:LOCALAPPDATA\Code\app-$ver\Code.exe"|code-block|syntax|javascript|2885593|将其保存为vscode.ps1并从命令行调用它，如下所示：|offset|length|style|CODE|2885594|powershell+".\vscode.ps1+-vars+@{+'NODE_ENV'='test';+'SOMETHING'='else'+}"|2885595|entityMap^0|0|0|5|A|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|$E|F]]|$1|G|3|H|5|6|7|S|8|@$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

as a workaround, you can set environment variables when starting VSCode, for example, using this little powershell script:

<pre><code>param(
 $vars = @{}
)

$vars.Keys | % {
 write-host "adding env variable: $_=$($vars[$_])"
 [Environment]::SetEnvironmentVariable($_, $vars[$_], "Process")
}
$ver = "0.1.0"
&amp; "$env:LOCALAPPDATA\Code\app-$ver\Code.exe"
</code></pre>

Save it as <code>vscode.ps1</code> and call it from commandline, like this:

<pre><code>powershell ".\vscode.ps1 -vars @{ 'NODE_ENV'='test'; 'SOMETHING'='else' }"
</code></pre>

blocks|key|542677|text|我正在使用env属性在launch.json中成功地传递它们|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|542678|{
++"version":+"0.2.0",
++"configurations":+[
++++{
++++++"type":+"pwa-node",
++++++"request":+"launch",
++++++"name":+"Launch+Program",
++++++"skipFiles":+[
++++++++"<node_internals>/**"
++++++],
++++++"program":+"${workspaceFolder}/index.js",
++++++"env":+{
++++++++"TEST_VAR":+"foo"
++++++}
++++}
++]
}|code-block|syntax|javascript|542679|entityMap^0|5|3|B|B|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|$]]

I'm successfully passing them using the <code>env</code> property in <code>launch.json</code>:
<pre><code>{
 &quot;version&quot;: &quot;0.2.0&quot;,
 &quot;configurations&quot;: [
 {
 &quot;type&quot;: &quot;pwa-node&quot;,
 &quot;request&quot;: &quot;launch&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;,
 &quot;env&quot;: {
 &quot;TEST_VAR&quot;: &quot;foo&quot;
 }
 }
 ]
}
</code></pre>

blocks|key|2885642|text|像这样，在你的操作系统下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2885643|++++++++"osx":+{
++++++++++++"MIMode":+"lldb",
++++++++++++"environment":+[{"name":+"DYLD_LIBRATY_PATH",+"value":+"/Users/x/boost_1_63_0/stage/lib/"}]
++++++++},|code-block|syntax|javascript|2885644|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|$]]

Like this, under your OS:

<pre><code> "osx": {
 "MIMode": "lldb",
 "environment": [{"name": "DYLD_LIBRATY_PATH", "value": "/Users/x/boost_1_63_0/stage/lib/"}]
 },
</code></pre>

blocks|key|2885711|text|自2016年末起，您还可以使用envFile+for+Node.js+projects|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|2885712|VS代码节点调试器现在支持从文件加载环境变量并将它们传递给节点运行时。https://github.com/Microsoft/vscode/issues/15964|blockquote|2885713|还请参阅：从外部文件(节点)加载环境变量：|2885714|若要使用此特性，请将属性envFile添加到启动配置中，并指定包含环境变量的文件的绝对路径：|2885715|For+Asp.Net+Core+projects，这个特性由vscode提供本机不支持，但它已经将最近添加到了omnisharp扩展中。该功能自2018年9月10日起通过v1.16.0提供。|2885716|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/Microsoft/vscode/issues/15964|1|https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_load-environment-variables-from-external-file-node|2|https://github.com/Microsoft/vscode/issues/46295|3|https://github.com/OmniSharp/omnisharp-vscode/pull/2462|4|https://github.com/OmniSharp/omnisharp-vscode/blob/master/CHANGELOG.md#1160-september-10-2018^0|F|7|N|K|0|Z|1C|0|0|5|F|1|0|0|0|P|13|5|2|1E|2|3|2E|7|4|0^^$0|@$1|2|3|4|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|1A|8|@]|E|@$9|1B|A|1C|1|1D]]|F|$]]|$1|J|3|K|5|6|7|1E|8|@]|E|@$9|1F|A|1G|1|1H]]|F|$]]|$1|L|3|M|5|I|7|1I|8|@]|E|@]|F|$]]|$1|N|3|O|5|6|7|1J|8|@$9|1K|A|1L|B|D]]|E|@$9|1M|A|1N|1|1O]|$9|1P|A|1Q|1|1R]|$9|1S|A|1T|1|1U]]|F|$]]|$1|P|3|-4|5|6|7|1V|8|@]|E|@]|F|$]]]|Q|$R|$5|S|T|U|F|$V|W]]|X|$5|S|T|U|F|$V|Y]]|Z|$5|S|T|U|F|$V|10]]|11|$5|S|T|U|F|$V|12]]|13|$5|S|T|U|F|$V|14]]]]

Since late 2016 you can also use the <code>envFile</code> for Node.js projects:

<blockquote>
 The VS Code Node debugger now supports to load environment variables from a file and passes them to the node runtime. <a href="https://github.com/Microsoft/vscode/issues/15964" rel="noreferrer">https://github.com/Microsoft/vscode/issues/15964</a>
</blockquote>

Also see: <a href="https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_load-environment-variables-from-external-file-node" rel="noreferrer">Load environment variables from external file (node)</a>: 

<blockquote>
 To use this feature, add an attribute envFile to your launch configuration and specify the absolute path to the file containing the environment variables:
</blockquote>

For Asp.Net Core projects, this feature <a href="https://github.com/Microsoft/vscode/issues/46295" rel="noreferrer">isn't supported natively</a> by vscode but it has <a href="https://github.com/OmniSharp/omnisharp-vscode/pull/2462" rel="noreferrer">recently</a> been added to the omnisharp vscode extension. This feature is available since September 10, 2018 via <a href="https://github.com/OmniSharp/omnisharp-vscode/blob/master/CHANGELOG.md#1160-september-10-2018" rel="noreferrer">v1.16.0</a>.

blocks|key|1586180|text|作为参考，我遇到了一个类似的问题(在2020年，在上述公认的答案中提到的错误被修正后很久)，我想指出一些不同的语言：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1586181|根据对启动配置的微软的文档编码，许多常见选项，包括"env"，都不是针对所有不同的调试/运行环境的重新定义的特性--也就是说，在我看来，不是VS代码为环境变量“提供”选项，而是选择特定的调试器扩展来实现这个特性。因此，|offset|length|style|CODE|1586182|调试应用程序意外崩溃|unordered-list-item|1586183|警告Property+"env"+is+not+allowed|1586184|可能是因为您使用的特定语言/调试器不支持或尚未实现对环境变量的处理。|1586185|正如qbiq所说，如果环境变量不会在启动过程中发生变化，那么解决这一问题的快速方法可能是导出它们，并使用这组特定的变量来运行VS代码。|1586186|entityMap|0|LINK|mutability|MUTABLE|url|https://code.visualstudio.com/Docs/editor/debugging#_launchjson-attributes^0|0|P|5|8|5|0|0|0|2|T|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@$D|12|E|13|1|14]]|A|$]]|$1|H|3|I|5|J|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|J|7|16|8|@$D|17|E|18|F|G]]|9|@]|A|$]]|$1|M|3|N|5|6|7|19|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

For reference, I came across a similar issue (in 2020, long after the bug mentioned in the accepted answer above was fixed) for a different language and would like to point out something:

Accoding to <a href="https://code.visualstudio.com/Docs/editor/debugging#_launchjson-attributes" rel="nofollow noreferrer">Microsoft's documentation</a> on launch configurations, many common options, including <code>"env"</code> are not requried features for all different debugging/run environments - that is to say, it seems to me that it is not VS Code that 'provides' the option for environment variables, but rather, the choice of the specific debugger extension to implement this feature. Therefore, either

<ul>
<li>An unexpected crash of the debugging application</li>
<li>the warning <code>Property "env" is not allowed</code></li>
</ul>

may occur because the particular language/debugger you are using doesn't support or hasn't implemented handling of environment variables.

As qbiq has said, probably a quick workaround for this if the environment variables are not going to change across launches would be to export them and run VS Code with this specific set of variables set.

blocks|key|2885742|text|我也遇到了同样的问题，结果发现我的项目根中有一个.env文件，它正在覆盖launch.json设置。已经警告过你了。:)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2885743|entityMap^0|O|4|10|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I had this same problem and it turns out I had a <code>.env</code> file in my project root which was overriding the <code>launch.json</code> settings. YOU'VE BE WARNED.
:)

blocks|key|1586252|text|这起作用了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1586253|​|1586254|📷|atomic|offset|length|1586255|1586256|只需添加以下内容|1586257|"env"：{+"NODE_ENV"："development“}|style|BOLD|1586258|"configurations":+[
++++{
++++++++"type":+"node",
++++++++"request":+"launch",
++++++++"name":+"Launch+Program",+//TODO:+cmd+as+launch+program
++++++++"skipFiles":+[
++++++++++++"<node_internals>/**"
++++++++],
++++++++"program":+"${workspaceFolder}\\index.js",
++++++++"env":+{
++++++++++++"NODE_ENV":+"development"
++++++++}
++++}
]|code-block|syntax|javascript|1586259|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/fee72b657bd6ce32d33ce87dee201eb6.png|imageAlt^0|0|0|0|1|0|0|0|0|0|X|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|15|8|@]|9|@$G|16|H|17|1|18]]|A|$]]|$1|I|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1A|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1B|8|@$G|1C|H|1D|N|O]]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1E|8|@]|9|@]|A|$S|T]]|$1|U|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11|12|-4]]]]

this is working

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

just add the following 

"env": {
 "NODE_ENV": "development"
 }

<pre><code>"configurations": [
 {
 "type": "node",
 "request": "launch",
 "name": "Launch Program", //TODO: cmd as launch program
 "skipFiles": [
 "&lt;node_internals&gt;/**"
 ],
 "program": "${workspaceFolder}\\index.js",
 "env": {
 "NODE_ENV": "development"
 }
 }
]
</code></pre>

blocks|key|1586298|text|在2020年6月，在OSX+Catalina+10.15.5上，这仍然是非常误导和打破的。我使用的是VSCode内部人士的CodeLLDB扩展版本1.5.3|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1586299|Version:+1.47.0-insider
Commit:+0913b1aa43191d8af0ccb4a133d9a8d7c1a81d69
Date:+2020-06-23T09:38:28.751Z+(1+day+ago)
Electron:+8.3.3
Chrome:+80.0.3987.165
Node.js:+12.13.0
V8:+8.0.426.27-electron.0
OS:+Darwin+x64+19.5.0|code-block|syntax|javascript|1586300|当使用env关键字在launch.json上启动调试器时，我得到以下结果：|CODE|1586301|​|1586302|📷|atomic|1586303|1586304|因此，简而言之，在"env"中使用launch.json指令将在屏幕截图中显示消息。这将阻止运行调试器，令人惊讶的是缺少功能，但足够公平。|1586305|但是，使用environment而不是env，没有出现错误消息弹出，但是在被调试的运行库中环境变量不可用，因此getenv(whatever)不返回该键的实际值:-！|1586306|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/dc34dc406cb0da0efc36dbc346e8239a.png|imageAlt^0|1P|H|0|0|3|3|A|B|0|0|0|1|0|0|0|9|5|H|B|0|5|B|J|3|1J|G|X|C|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|19|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1A|8|@$9|1B|A|1C|B|M]|$9|1D|A|1E|B|M]]|D|@]|E|$]]|$1|N|3|O|5|6|7|1F|8|@]|D|@]|E|$]]|$1|P|3|Q|5|R|7|1G|8|@]|D|@$9|1H|A|1I|1|1J]]|E|$]]|$1|S|3|O|5|6|7|1K|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|1L|8|@$9|1M|A|1N|B|M]|$9|1O|A|1P|B|M]]|D|@]|E|$]]|$1|V|3|W|5|6|7|1Q|8|@$9|1R|A|1S|B|M]|$9|1T|A|1U|B|M]|$9|1V|A|1W|B|M]|$9|1X|A|1Y|B|C]]|D|@]|E|$]]|$1|X|3|-4|5|6|7|1Z|8|@]|D|@]|E|$]]]|Y|$Z|$5|10|11|12|E|$13|14|15|-4]]]]

On june 2020 this is still very misleading and broken on OSX Catalina 10.15.5. I am using VSCode insiders with CodeLLDB extension version 1.5.3:
<pre><code>Version: 1.47.0-insider
Commit: 0913b1aa43191d8af0ccb4a133d9a8d7c1a81d69
Date: 2020-06-23T09:38:28.751Z (1 day ago)
Electron: 8.3.3
Chrome: 80.0.3987.165
Node.js: 12.13.0
V8: 8.0.426.27-electron.0
OS: Darwin x64 19.5.0
</code></pre>
When launching the debugger with the <code>env</code> keyword on <code>launch.json</code> I get this:
<a href="https://i.stack.imgur.com/aU1JG.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/aU1JG.png" alt="enter image description here" /></a>
So in a nutshell, using <code>&quot;env&quot;</code> directive in <code>launch.json</code> will show up the message in the screenshot. This will prevent running the debugger, surprising lacking feature, but fair enough.
But then, using <code>environment</code> instead of <code>env</code>, there's no error message popping up but the environment variables are not available on the runtime being debugged, so <code>getenv(whatever)</code> does not return the actual value for that key :-!

blocks|key|2885900|text|版本1.49.1|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2885901|可以通过在env文件中使用launch.json属性或使用值为.env文件位置的envFile属性来添加env变量。|CODE|2885902|警告:如果您已经有一个.env文件，它将自动包含它。(每条反岛民评论)|2885903|环境规划实例：|2885904|{
++...
+++"env":+{+"PORT":+"4000"+}
++...
}|code-block|syntax|javascript|2885905|envFile示例：|2885906|{
++...
++"envFile":+"${workspaceFolder}/server/.env",
++...
}|2885907|entityMap^0|0|8|0|5|3|14|7|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@$9|11|A|12|B|H]|$9|13|A|14|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|15|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|16|8|@]|D|@]|E|$]]|$1|M|3|N|5|O|7|17|8|@]|D|@]|E|$P|Q]]|$1|R|3|S|5|6|7|18|8|@]|D|@]|E|$]]|$1|T|3|U|5|O|7|19|8|@]|D|@]|E|$P|Q]]|$1|V|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|W|$]]

Version 1.49.1
You can add env variables by using the <code>env</code> property in your launch.json file or by using the <code>envFile</code> property with the value being the location of your .env file.
Warning: If you already have a .env file it auto includes it. (per denislexic comment)
env example:
<pre><code>{
 ...
 &quot;env&quot;: { &quot;PORT&quot;: &quot;4000&quot; }
 ...
}
</code></pre>
envFile example:
<pre><code>{
 ...
 &quot;envFile&quot;: &quot;${workspaceFolder}/server/.env&quot;,
 ...
}
</code></pre>

blocks|key|542947|text|它使用envFile变量为我的django项目工作。您可以签出以下链接：https://code.visualstudio.com/docs/editor/debugging|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|542948|{
+++"version":+"0.2.0",
++++"configurations":+[
++++++++{
++++++++++++"name":+"Python:+Django",
++++++++++++"type":+"python",
++++++++++++"request":+"launch",
++++++++++++"program":+"${workspaceFolder}/project/manage.py",
++++++++++++"args":+[
++++++++++++++++"runserver"
++++++++++++],
++++++++++++"django":+true,
++++++++++++"envFile":+"${workspaceFolder}/project/Server/settings/local.env"
++++++++}
++++]
}|code-block|syntax|javascript|542949|entityMap|0|LINK|mutability|MUTABLE|url|https://code.visualstudio.com/docs/editor/debugging^0|3|7|10|1F|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@$9|V|A|W|1|X]]|E|$]]|$1|F|3|G|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

It worked for my django project using the <code>envFile</code> variable.
You can checkout this link: <a href="https://code.visualstudio.com/docs/editor/debugging" rel="nofollow noreferrer">https://code.visualstudio.com/docs/editor/debugging</a>
<pre><code>{
 &quot;version&quot;: &quot;0.2.0&quot;,
 &quot;configurations&quot;: [
 {
 &quot;name&quot;: &quot;Python: Django&quot;,
 &quot;type&quot;: &quot;python&quot;,
 &quot;request&quot;: &quot;launch&quot;,
 &quot;program&quot;: &quot;${workspaceFolder}/project/manage.py&quot;,
 &quot;args&quot;: [
 &quot;runserver&quot;
 ],
 &quot;django&quot;: true,
 &quot;envFile&quot;: &quot;${workspaceFolder}/project/Server/settings/local.env&quot;
 }
 ]
}
</code></pre>

Working with the new VSCode editor on a node.js project. I am attempting to configure my "Launch" profile for debugging by editing the launch.json file. I need to setup a connectionstring as an environment variable. According to the comments in the launch.json file:

<pre><code>// Environment variables passed to the program.
"env": { }
</code></pre>

I have tried adding my environment variable like so:

<pre><code>"env":
{
"CONNECTION_STRING": "Data Source=server;Initial Catalog=catalog;User ID=uid;Password=pwd;MultipleActiveResultSets=true"
}
</code></pre>

This causes an error when I try to launch my app; "OpenDebug process has terminated unexpectedly". I have not yet found any log files, etc. that might explain what the issue is.

I know this app works correctly when I setup the environment variable and launch my app from the standard command prompt. The app also runs as expected if I comment out my variable in the launch.json file; I just can't connect to the database.

I am assuming that I am using the wrong format in the launch.json file, but I have not yet found any way to make this work.

Any ideas?

How do I add environment variables to launch.json in VSCode

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

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

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

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

社区新版编辑器体验调研

在VSCode项目上使用新的node.js编辑器。我试图通过编辑launch.json文件来配置我的“启动”配置文件以进行调试。我需要将连接字符串设置为环境变量。根据launch.json文件中的注释：// Environment variables passed to the program."env": { }我尝...

问如何在launch.json中VSCode中添加环境变量
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在launch.json中VSCode中添加环境变量EN