Closed BerndWessels closed 8 years ago
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 Indeed sounds like a good idea. So, as you did set it up and working, can't you provide a pull request with proper code snippets/comments related to this issue for readme, please? If you want, of course!
Cheers
@Va1 I made a pull request to extend the readme with more information. Cheers Bernd
@BerndWessels Looks cool! I did some corrections in order to make it less verbose and more structured, hope you'll like it. Thank you!
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
: