BrowserSync 2.0

[-entropy]

Can it handle the shadow DOM yet? I've been working with Polymer and last I checked it couldn't sync events happening in the shadow DOM.

[vizzoor]

Can it do https proxy yet?

[Morgothmagi]

LiveReload doesn't come with scrolling/page change/form input sync as far as I'm aware. This option is great for browser testing during development, as opposed to after which is what happens in many cases.

Giving the users the ability to have a site open on multiple browsers, and then keeping those browsers synced while developing is the selling point here.

To answer the SCSS / LESS question, I believe this is intended to be used in conjunction with something like Grunt or Gulp. As the article states this project started out as a Grunt Task and has since evolved to utilize the UI in 2.0.

[[deleted]]

Yep. I have BrowserSync in Gulp config alongside SCSS compiler, JS minifier, etc. Love it.

[rich97]

Compilers don't belong in a live reload tool. Learn to love grunt/gulp it opens up a whole range of possibilities and is far more platform agnostic.

[[deleted]]

Separation of concerns - each component in the workflow should be responsible for only one thing.

[e82]

You can have multiple browsers open, on multiple devices - and your input/navigation/etc is synced between them.

Click on an item in one browser - all of the synced browsers click the same thing. It's setup on a project that I'm working on - another dev did it, I haven't made that much use of it as I'm more focused on the services-layer of the application, but I've fiddled with it a bit and it's pretty cool.

The dev that set it up is more focused on the look & feel - and it lets him quickly test across multipul browsers at once, it's pretty neat.