Error ECONNREFUSED is thrown on Windows for chrome on a clean project
Open
Nobody has claimed this yet.
pending-triage
- Dominant language
- TypeScript
- Stars
- 10.5k
- Forks
- 564
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When I run pnpm dev I get the error after ~30sec.
pnpm dev -b firefox, works and loads firefox.
-b chrome or no -b fails as shown below.
Identical issue to #766 except for windows 10 and chrome.
> wxt-react-starter@0.0.0 dev
> wxt
WXT 0.20.7 1:29:44 PM
√ Started dev server @ http://localhost:3000 1:29:44 PM
i Pre-rendering chrome-mv3 for development with Vite 6.3.5 1:29:44 PM
√ Built extension in 679 ms 1:29:45 PM
├─ .output\chrome-mv3-dev\manifest.json 1.05 kB
├─ .output\chrome-mv3-dev\popup.html 777 B
├─ .output\chrome-mv3-dev\background.js 20.06 kB
├─ .output\chrome-mv3-dev\chunks\popup-f02QKjXp.js 8.07 kB
├─ .output\chrome-mv3-dev\content-scripts\content.js 25.17 kB
├─ .output\chrome-mv3-dev\icon\128.png 3.07 kB
├─ .output\chrome-mv3-dev\icon\16.png 559 B
├─ .output\chrome-mv3-dev\icon\32.png 916 B
├─ .output\chrome-mv3-dev\icon\48.png 1.33 kB
├─ .output\chrome-mv3-dev\icon\96.png 2.37 kB
└─ .output\chrome-mv3-dev\wxt.svg 1.07 kB
Σ Total size: 64.45 kB
× Command failed after 28.8 s 1:30:13 PM
ERROR connect ECONNREFUSED 127.0.0.1:52967 1:30:13 PM
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16)
Reproduction
Steps to reproduce
pnpm dlx wxt@latest init test --template react
cd test
pnpm i
pnpm run dev
System Info
System:
OS: Windows 10 10.0.19045
CPU: (16) x64 Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz
Memory: 19.11 GB / 31.84 GB
Binaries:
Node: 22.15.0 - C:\web\nodejs\node.EXE
npm: 10.9.2 - C:\web\nodejs\npm.CMD
pnpm: 10.12.4 - C:\web\nodejs\pnpm.CMD
Browsers:
Chrome: 139.0.7258.67 (Official Build) (64-bit)
Internet Explorer: 11.0.19041.5794
npmPackages:
"wxt": "^0.20.6"
"web-ext": "8.9.0"
Used Package Manager
pnpm
Validations
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #766, then reproduce the problem with the listed pnpm commands on Windows using Chrome and Firefox. Trace why Chrome's dev launch reaches ECONNREFUSED at 127.0.0.1 and verify that pnpm run dev loads Chrome successfully without breaking the working Firefox path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript, vite
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100