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

[3.0.0-alpha6] Only the last websocket client gets messages #1248

Closed
1 of 3 tasks
dev357 opened this issue Dec 29, 2017 · 1 comment
Closed
1 of 3 tasks

[3.0.0-alpha6] Only the last websocket client gets messages #1248

dev357 opened this issue Dec 29, 2017 · 1 comment

Comments

@dev357
Copy link

dev357 commented Dec 29, 2017

  • Operating System: Windows 10
  • Node Version: 9.3.0
  • NPM Version: 5.4.2
  • webpack Version: 4.0.0-alpha.2
  • webpack-dev-server Version: 3.0.0-alpha6
  • This is a bug
  • This is a feature request
  • This is a modification request

Expected Behavior

when connecting multiple clients to the server all of them should receive updates through the websocket connection

Actual Behavior

only the client that connected last will receive updates

For Bugs; How can we reproduce the behavior?

connect two clients to the devserver. Update a file that should cause a refresh. Only the client that was connected last will receive the reload event.

Notes

from what i can tell, the DevServer class can only save a single socket connection. It is overwritten when a new connection is established.

lpinca added a commit to lpinca/webpack-dev-server that referenced this issue Jan 7, 2018
Send data to all connected clients.

Fixes: webpack#1248
@shellscape
Copy link
Contributor

All, @next is no longer being worked on. The team has decided in a change of direction. More info to follow, but you should consider the alpha versions of 3.0.0 unsupported.

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

2 participants