要在VS Code中設(shè)置調(diào)試環(huán)境變量，需在launch.json文件中使用"environment"數(shù)組配置。具體步驟如下：1. 在launch.json的調(diào)試配置中添加"environment"數(shù)組，以鍵值對形式定義變量，如API_ENDPOINT和DEBUG_MODE；2. 可通過.env文件加載變量，提升管理效率，並在launch.json中使用envFile指定文件路徑；3. 若需覆蓋系統(tǒng)或終端已設(shè)變量，直接在launch.json中重新定義即可；4. 注意確保launch.json位置正確、避免格式錯誤，並可利用${env:VAR_NAME}引用現(xiàn)有變量。此方法適用於多種語言，且僅在調(diào)試會話期間生效。

Setting environment variables for debugging in VS Code is straightforward once you know where to look. The key is to configure your launch.json file properly, which controls how the debugger starts and what settings it uses.

Here are a few common scenarios and how to handle them:

1. Setting Environment Variables in launch.json

When debugging an app in VS Code, most configurations are handled in the .vscode/launch.json file. To set environment variables, use the "environment" array inside your configuration.

Example:

 {
  "type": "pwa-chrome",
  "request": "launch",
  "name": "Launch Chrome against localhost",
  "url": "http://localhost:8080",
  "webRoot": "${workspaceFolder}/src",
  "environment": [
    {
      "name": "API_ENDPOINT",
      "value": "https://dev-api.example.com"
    },
    {
      "name": "DEBUG_MODE",
      "value": "true"
    }
  ]
}

This method works well for JavaScript, TypeScript, Node.js, and other languages that support debugging through VS Code's built-in or extension-based debuggers.

If you're using a different runtime (like Python or Go), make sure to check the syntax for setting environment variables — but the overall idea stays the same: define them under the "environment" key in your launch configuration.

2. Using env Files for Cleaner Setup

Instead of hardcoding values directly into launch.json , you can load them from an .env file. This keeps sensitive or frequently changing values separate and easier to manage.

• First, create a .env file in your project root:

   API_ENDPOINT=https://staging-api.example.com
  DEBUG_MODE=true

• Then, use an extension like Env File or DotENV Debug Config to load these variables in your launch.json . Here's how it might look:

   {
  "type": "node",
  "request": "launch",
  "name": "Launch Node.js with .env",
  "runtimeExecutable": "nodemon",
  "restart": true,
  "console": "integratedTerminal",
  "internalConsoleOptions": "neverOpen",
  "envFile": "${workspaceFolder}/.env"
  }

  This approach is especially useful when working in teams or across multiple environments (development, staging, testing).

  3. Overriding System or Shell Environment Variables

  Sometimes, your terminal or system may already have certain environment variables set. If you want to override those during debugging, just define the variable again in your launch.json .

  For example, if your shell has DEBUG_MODE=false , but you want to force it to true while debugging, simply include it in the "environment" block as shown earlier.

  Alternatively, if you're launching VS Code from the terminal, any variables exported there will be inherited by the debugger unless explicitly overridden.

  4. Common Pitfalls and Tips

  Here are a few things to keep in mind:

  • Make sure your .vscode/launch.json is in the right folder — each workspace can have its own.
  • Environment variables only apply during the debug session — they don't persist beyond that.
  • Use ${env:VAR_NAME} in launch.json to reference existing environment variables if needed.
  • For complex setups, consider using different configurations in launch.json for dev, test, and staging.

  基本上就這些。 It's not complicated, but easy to overlook small formatting issues or misconfigurations that prevent variables from being picked up correctly.

  以上是如何在VSCODE設(shè)置中設(shè)置環(huán)境變量？的詳細內(nèi)容。更多資訊請關(guān)注PHP中文網(wǎng)其他相關(guān)文章！