-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Using socket.io in the dev-server? #76
Comments
The problem is that socket.io tries to connect to
|
@jhnns wouldn't it be a better solution to configure webpack-dev-server so it doesn't intercept |
Hi @ArnoBuschmann , did you manage to find a good solution? I'm having the same problem. |
@ocyedwin yes, simply rename the path of your own socket. Right now the hot-loader is using |
@wmertens okay, thanks! |
I wasn't able to use socket.io + webpack-dev-server. But like @jhnns mentioned using webpack-dev-middleware in addition to https://www.npmjs.com/package/webpack-hot-middleware gives you hot-reloading without webpack-dev-server |
I think this issue could be fixed if #220 was implemented? Then the hot loader could listen to a custom url path that does not conflict with the app, such as /__webpack-dev/socket.io |
Yup. On Sat, Aug 8, 2015, 18:53 scottmcnab notifications@github.com wrote:
Wout. |
I am running into the same problem, is there any better solution than rename the apps io path (which will likely leads to more problems down the road)? |
As of v0.13 (#302) socket.io is replaced with sockjs, so you would no longer have this problem. |
I wanted to use socket.io in my project, so I added this to the express server.js file:
Now when creating a production build, the socket communication between client and server works nicely as expected.
But: Unfortunately it is not working when running the Webpack dev server :(
Has anyone an idea how that could be fixed?
The text was updated successfully, but these errors were encountered: