Closed HashandSalt closed 6 years ago
I can confirm the issue. Just did a npm update today and it stopped working.
@HashandSalt @alesvaupotic what versions of node are you using? I'll do some tests with laravel-mix when I get the chance
Phew! glad its not just us. Running on Node 8.9.1 on a Mac (High Sierra).
Ubuntu 16.04.4 LTS
ales@r35:/var/www/$ node -v
v8.10.0
ales@r35:/var/www/$ npm -v
5.7.1
Not sure about which version was last used, I just did an update as part of my weekly routine.
Went back and found out the last working version for me is 2.0.1.
@HashandSalt Alright, I figured node version wasn't the issue but had to check. The repo link you provided is a link to this thread, can you provide the right link? Thanks
Oh whoops, sorry, ive fixed the link.
@HashandSalt @alesvaupotic Guys, in the meantime you can check out this temporary fix: https://github.com/JeffreyWay/laravel-mix/issues/1538
Edit: fixed link
Thanks, my fix exactly. I hardcoded it also to 2.0.1 and it's been fine since.
@HashandSalt @alesvaupotic I fixed it here https://github.com/Va1/browser-sync-webpack-plugin/pull/67 Just needs to merged.
fix was shipped with version 2.2.2. thanks guyz
Works like a charm. Thanks!
Version 2 seems to break with Laravel Mix. Webpack says its building but fails to launch the browser, and browsersync. Webpack says its watching files and then almost immediately says its done and drops back to terminal prompt.
This breaks:
This works
Any idea what the problem could be? Trouble is, Mix auto installs the most recent version of
browser-sync-webpack-plugin
so i'm sure I won't be the only person to run into it.I'm using it standalone, not in a Laravel project.