Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Can not use env variables in the launch.json

Open
#264 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
devtools

Research direction

Start with the Firefox configuration in launch.json and reproduce the issue using the provided DEVSERVER_PORT environment variable. Compare its URL handling with the working Chrome configuration; done means the Firefox debugger resolves the variable and connects to the configured http://localhost port without hardcoding it.

Written by the indexing model from the issue text.

Description

Hello,
I am trying to make debugger configurations pointing to a port specified in the enviromental variables. It works for chrome and for edge but it does not with the firefox debugger.

            "type": "firefox",
            "request": "launch",
            "name": "Debug React - Firefox",
            "url": "http://localhost:${env:DEVSERVER_PORT}/",
            "webRoot": "${workspaceFolder}/react_front/src",
            "pathMappings": [
                {
                    "url": "http://localhost:${env:DEVSERVER_PORT}/workspaces/project/react_front/src",
                    "path": "${workspaceFolder}/react_front/src"
                }
            ]

with this configuration it tries to connect to https://localhost instead to http://localhost:3000 (for example), but if I hardcode the port instead it works just fine.

On the other side this configuration works for chrome

            "type": "pwa-chrome",
            "request": "launch",
            "name": "Debug React - Chrome",
            "url": "http://localhost:${env:DEVSERVER_PORT}",
            "webRoot": "${workspaceFolder}/react_front/src",

So I don't know if this is a bug, or if there is any workaround to solve this problem. But the harcoded option is really bad because the other devs are going to set their ports and commit them, and CAOS.

Thank you.

Dominant language
TypeScript
Stars
447
Forks
76
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firefox-devtools/vscode-firefox-debug

All issues in firefox-devtools/vscode-firefox-debug

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.