Do you want to request a feature or report a bug?
bug
What is the current behavior?

rails/webpacker#570
source code: https://github.com/AirDwing/vuetify-demo
If the current behavior is a bug, please provide the steps to reproduce.
have no idea
What is the expected behavior?
perhaps it's related to devserver
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
This issue was moved from webpack/webpack#5490 by @sokra. Orginal issue was by @willin.
mark
@willin the config and setup for your project is rather complex and we're unable to nail down a root cause. it looks like it might be sockjs related, but I couldn't say for sure. given that we're going to replace sockjs with a native WebSocket solution in v3, this particular issue isn't something we're going to look into further I'm afraid.
if you find the cause and can point that out, we'd be happy to look at getting a stop-gap fix in a patch release for you, but until then we're going to close this as wont-fix.
I've run into the same issue here:

Current solution is to stop webpack-dev-server and re-run~
BTW, what's the schedule to replace sock.js?
@noscripter there's not schedule as far as dates and times (we're all just donating our free time). it's an item in Milestone 3, however. The issues that are slated to be resolved for version 3 can be seen here https://github.com/webpack/webpack-dev-server/milestone/1.
I am having the same issue
@FourSeventy please do not post "me too" or "same issue" replies on issues or pull requests. instead, use github reactions on the original post.