This repository has been archived by the owner on Aug 21, 2020. It is now read-only.
Update devServer.js #111
Merged
Update devServer.js #111
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Remove localhost binding so allow express to listen universally on port 3000. This fixes #89.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove localhost binding so allow express to listen universally on port 3000. This fixes #89. On Windows, when you have multiple network gateways (for my case, it was because I am on a corporate VPN), express gets quite particular about how it resolves. For some reason, the general request resolves fine, but the HMR requests don't. But when you allow express to be unbound from the hostname, it then allows HMR to work properly.