dev websocket connection failed

Describe the bug

After executing "run dev", the websocket reported an error, and the content script did not execute successfully, but no error message was reported.

Reproduction

bunx wxt@latest init

The default template already has this issue.

Steps to reproduce

No response

System Info

System:
    OS: macOS 15.3
    CPU: (8) arm64 Apple M1 Pro
    Memory: 515.16 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.9.0 - ~/Library/Caches/fnm_multishells/19945_1737477607928/bin/node
    Yarn: 1.22.22 - ~/Library/Caches/fnm_multishells/19945_1737477607928/bin/yarn
    npm: 10.8.3 - ~/Library/Caches/fnm_multishells/19945_1737477607928/bin/npm
    pnpm: 9.11.0 - ~/Library/Caches/fnm_multishells/19945_1737477607928/bin/pnpm
    bun: 1.1.43 - ~/.bun/bin/bun
  Browsers:
    Chrome: 132.0.6834.83
    Safari: 18.3
  npmPackages:
    wxt: ^0.19.13 => 0.19.24

Used Package Manager

bun

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.

Start by creating the default template with bunx wxt@latest init and running it with run dev, then inspect the development WebSocket and content-script error handling. Use the captured failure to locate the relevant dev-server entry point; done means the default template’s content script executes successfully and a useful error is reported when the connection fails.