Skip to content

WebSocket connection to 'ws://localhost/' failed: #648

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

Open
1 of 2 tasks
tjx666 opened this issue Feb 20, 2023 · 3 comments
Open
1 of 2 tasks

WebSocket connection to 'ws://localhost/' failed: #648

tjx666 opened this issue Feb 20, 2023 · 3 comments
Assignees

Comments

@tjx666
Copy link

tjx666 commented Feb 20, 2023

Build tool

Vite

Where do you see the problem?

  • In the browser
  • In the terminal

Describe the bug

image

I can still reproduce this in latest @crxjs/vite-plugin version: 2.0.0-beta.12

Reproduction

  1. git clone [email protected]:thetarnav/solid-devtools.git
  2. pnpm install
  3. pnpm dev:ext
  4. load extension at packages/extension/dist

Logs

No response

System Info

System:
    OS: macOS 13.2.1
    CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
    Memory: 142.24 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.14.1 - ~/Library/Caches/fnm_multishells/36587_1676917501753/bin/node
    npm: 9.5.0 - ~/Library/Caches/fnm_multishells/36587_1676917501753/bin/npm
  Browsers:
    Chrome: 110.0.5481.100
    Chrome Canary: 112.0.5607.0
    Firefox: 109.0.1
    Firefox Developer Edition: 111.0
    Safari: 16.3
  npmPackages:
    vite: ^4.1.1 => 4.1.1
    @crxjs/vite-plugin: ^1.0.14

Severity

annoyance

@cutsin
Copy link

cutsin commented Feb 23, 2023

Specify a port number can resolve this:

// vite.config.ts
{
  server: { port: 3000, hmr: { port: 3000 } }
}

@jacksteamdev jacksteamdev self-assigned this Mar 26, 2023
iMuFeng added a commit to iMuFeng/extension-starter that referenced this issue May 8, 2023
@octavio1243
Copy link

Image

Image

Image

Copy link
Contributor

⚠️ Important Notice: CRXJS is seeking new maintainers.

  • New issues and PRs may not receive immediate attention
  • A new maintenance team must establish itself by March 31, 2025 or this repository will be archived on June 1, 2025
  • Learn more about the transition

This is an automated message. Please do not reply to this comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants