Configure browser binaries globally on windows
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10.5k
- Forks
- 564
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
The web-ext.config.ts in the project directory is working just fine. I'm trying to use it globally as mentioned in the docs by putting it in ~/web-ext.config.ts , but for windows I believe the path is C:\Users\<username>\. I tried changing the file name to .web-ext-config.js as in here but with not luck.
To Reproduce
- Start dev mode:
npm run dev
Expected behavior
Launch browser binaries specified in C:\Users\<username>|web-ext.config.ts
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
System:
OS: Windows 10 10.0.19045
CPU: (8) x64 Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz
Memory: 9.46 GB / 15.86 GB
Binaries:
Node: 20.10.0 - C:\Program Files\nodejs\node.EXE
npm: 10.2.3 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Chromium (123.0.2420.97)
Internet Explorer: 11.0.19041.3636
npmPackages:
wxt: ^0.18.2 => 0.18.2
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 with the global web-ext.config.ts discovery path used when running npm run dev, and compare its Windows home-directory handling with the documented automatic discovery behavior. Done means a configuration at C:\Users<username>\web-ext.config.ts is found on Windows and the specified browser binaries launch in dev mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100