[Enhancement] Replace livereload with browserSync()

[flick36]

Since elixir version 5.1 we have the browserSync() task by default, that it's a replacement for the livereload plugin in this starter, the most awesome thing that livereload does it's the soft CSS reload but that seems broken now because of the use of the task versions() and it brokes every single time you made a save too fast for example you modify a typo in 2 files and you save them almost instantly it will brake because it's lock, this doesn't happens with browserSync() the only tiny problem it's that in order to browserSync() to work we have to initialize artisan serve like: artisan serve --host=0.0.0.0 and the task would look like this: .browserSync({ proxy: 'localhost:8000' })

[jadjoubran]

Yes indeed live reload broke because of the versioning task..
This wouldn't be fixed in browserSync though since we'll have the same issue

But I still see the benefit of removing laravel-elixir-reload and relying on elixir..
So yeah why not 😄
In case you decide to work on it, please let me know so that we don't work on it at the same time

[flick36]

Well it's really simply, by just removing the livereload and putting .browserSync({ proxy: 'localhost:8000' }) instead, you are ready to go

i can create a PR if you want

[jadjoubran]

Actually aren't we missing a script for browser sync to work? It's not working right now

[flick36]

I've downloaded a clean starter, replace what i changed and it worked, the script in the browser is set automatically by browserSync() and you have to start artisan seve with a --host=0.0.0.0 argument

[jadjoubran]

ah.. I missed the host argument
Thanks for giving it a try
I'll keep this open until I update the docs and release 3.2.1

[flick36]

There's a workaround to make artisan serve starts by default in 0.0.0.0 host by creating a task inside gulp, and that way with just gulp && gulp watch the server will start automtically, but it's not a general solution because it implies the user to set the location to the php path and it's different for every user and SO. but maybe with the implement of #149 or maybe writing in the docs a how-to for those who might want to do that?

[jadjoubran]

Yeah it would be a bit overcomplicated..
I was thinking of creating a gulp serve task that runs gulp and then 2 parallel processes: gulp watch and artisan serve
But I'll just update the docs for now

[jadjoubran]

This has become a bit redundant now that Laravel valet exists.. What do you think?
I'm personally just using valet since it makes more sense to just go to the url rather than having to run artisan serve --host=0.0.0.0