After running the npm run dev command, the extension does not automatically load when the Chrome window starts.

[zhayes]

Describe the bug

"wxt": "^0.20.8", node version: v22.11.0; macOS: 15.5 (24F74);

Reproduction

Steps to reproduce

No response

System Info

System:
    OS: macOS 15.5
    CPU: (8) arm64 Apple M1
    Memory: 132.42 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.11.0 - /Users/chad/.nvm/versions/node/v22.11.0/bin/node
    npm: 10.9.0 - /Users/chad/.nvm/versions/node/v22.11.0/bin/npm
    pnpm: 10.3.0 - /Users/chad/.nvm/versions/node/v22.11.0/bin/pnpm
    Deno: 2.3.7 - /Users/chad/.deno/bin/deno
  Browsers:
    Chrome: 142.0.7444.60
    Firefox: 141.0
    Safari: 18.5
  npmPackages:
    wxt: ^0.20.8 => 0.20.8

Used Package Manager

pnpm

Validations

• [x] Read the Contributing Guidelines.
• [x] Read the docs.
• [x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• [x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• [x] The provided reproduction is a minimal reproducible example of the bug.

[sklaboi]

Same here, can confirm

[antonipelka]

I had similar issue for v0.20.7 and got it resolved by updating to v0.20.11. Also running on MacOS and Node 22.

https://wxt.dev/guide/resources/upgrading.html

[ImTheCodeFarmer]

I had similar issue for v0.20.7 and got it resolved by updating to v0.20.11. Also running on MacOS and Node 22.

https://wxt.dev/guide/resources/upgrading.html

+1 here

[emiliioaguirre]

Upgrading to WXT 0.20.11 solves this issue. Tested on macOS Sequoia + Chrome v142

bun install wxt@latest --ignore-scripts
bun wxt prepare

[PatrykKuniczak]

@zhayes If it's really fixed, let's close this issue :)

[sklaboi]

Upgrading to WXT 0.20.11 solves this issue. Tested on macOS Sequoia + Chrome v142

bun install wxt@latest --ignore-scripts bun wxt prepare

Upgrading to WXT 0.20.11 fixes the auto-load, but Chrome becomes unusable when the extension triggers any Google login flow.

When trying to sign in (OAuth or Firebase auth via Google), Chrome shows this screen:

“Couldn’t sign you in — This browser or app may not be secure. Try using a different browser.”

So the browser session started by wxt dev isn’t considered a secure environment for Google OAuth, which breaks extension debuging that depend on it. Anyone know a fix for this maybe? Tried searching, but nothing worked.

[PatrykKuniczak]

@sklaboi That's known issue #1890

[nickbar01234]

Tried bumping to 0.20.11, but it doesn't seem to solve the problem. The behaviors I'm observing

• [Occasionally] Manifest does not load unpack automatically -- I'm not sure how to reproduce this behavior
• [Consistently] Content script is not injected until I refresh browser for the first time