-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
Passing in hot: false does not disable HMR #85
Comments
Thanks for the issue but this isn't a problem with You should also resolve this error:
It's very relevant, actually. If you have another socket server running off of different/other settings, it's going to mess up the instance you're trying to run. I'd recommend passing a different port to the Looking at |
Thanks for the reply. What I meant was that it seems the other server listening on 8081 must be an existing webpack-hot-clien websockets server that didnt get closed when I SIGINT’ed my previous run of the script. At any rate you’re right, I should simply just use webpack-dev-middleware. Thank you for the advice and help. |
['dev'] is an invalid additional property? why? |
@liubin915249126 it's considered poor form to ask an off-topic question in an issue thread. Please do have a read about Github etiquette. Your question is what is called "thread jacking." Read the README, that's not a valid option. |
If you have a large amount of code to share which demonstrates the problem you're experiencing, please provide a link to your
repository rather than pasting code. Otherwise, please paste relevant short snippets below.
Expected Behavior
No websocket server should start.
Actual Behavior
Websocket server starts, and the client page tries to connect.
The
EADDRINUSE
is irrelevant, of course, the server must still be running from a previously-killed process. However I would expect the server not to try to start at all.How can we reproduce the behavior?
The text was updated successfully, but these errors were encountered: