Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure browser binaries globally on windows #659

Open
yacine-bens opened this issue May 15, 2024 · 1 comment
Open

Configure browser binaries globally on windows #659

yacine-bens opened this issue May 15, 2024 · 1 comment
Labels
bug Something isn't working upstream Issue related to an upstream library
Milestone

Comments

@yacine-bens
Copy link
Contributor

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

  1. 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
@yacine-bens yacine-bens added the pending-triage Someone (usually a maintainer) needs to look into this to see if it's a bug label May 15, 2024
@aklinker1
Copy link
Collaborator

I looked into this, and I think this is a problem with c12. It's not discovering the config file in the home directory correctly.

@aklinker1 aklinker1 added bug Something isn't working upstream Issue related to an upstream library and removed pending-triage Someone (usually a maintainer) needs to look into this to see if it's a bug labels Jul 2, 2024
@aklinker1 aklinker1 added this to the v1.0 milestone Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working upstream Issue related to an upstream library
Projects
None yet
Development

No branches or pull requests

2 participants