-
Notifications
You must be signed in to change notification settings - Fork 40
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
404 Cannot GET / #8
Comments
Hey @BerndWessels ! As you can read out in #4 (latest comments in particular), webpack should be serving and browser-sync should be proxying. But, personally, I did not try to set up the stuff this way. Or I may have misunderstood your needs, let me know if this helps you. |
@Va1 Hi, yes thank you. It took a while to get it right. I think this is worth putting into the Git Readme - since this is a complicated but very common configuration. And finding the proxying information somewhere berried in a closed Git Issue is not really a good starting point. Thank you |
@BerndWessels Cheers |
@Va1 |
@BerndWessels |
Hi
I can't get it to work - and I actually don't see how it possible since webpack serves from memory and not the file system.
Webpack serves well on
localhost:8080
but BrowserSyncPlugin onlocalhost:3000
returns 404.This is the config I use with
BUILD = false
andTEST = false
:The text was updated successfully, but these errors were encountered: