-
-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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
Allow bind Webpack to 0.0.0.0 #137
Comments
This will be doable with #128! |
Yep, we’ll probably go with #128—just want to make some other things work there first. |
#128 should have fixed this. |
Ok, thanks for the quick feedback guys. |
This should be fixed in 0.2.0 alpha, mind giving it a spin to confirm? Here's how: #190 |
It seems that it is now public by default but you may have a flag in your package.json {private: true} that you need to set to false. |
As far I've seen,
npm start
start webpack serving from localhost:3000.It would be nice an option to bind IP 0.0.0.0 to webpack, like the option
--host 0.0.0.0
Webpack already accept today.This is specially useful when starting server from inside a Docker container: even mapping the port 3000 to localhost, Webpack doesn't accepts connections from outside the container.
The text was updated successfully, but these errors were encountered: