Electron support
This release includes the addition of a few new options.
script.domain
for situations where you want full control over the domain used to serve the client JSlocalOnly
for situations where you need to opt-out of Browsersync's dynamic host rewriting.
See the previous discussion for details, but here's the tl;dr:
Browsersync goes out of it's way to 'just work' in most use-cases - but this requires some dynamic aspects that are OTT for something as simple as an Electron workflow, where you probably just want to reload files when they change.
Electron users
To have Browsersync watch over your files and reload your app when they change, just use the localOnly
flag & then copy/paste the snippet into your footer.
cli
browser-sync start --localOnly --files './app'
api
const bs = require('browser-sync').create();
bs.init({
localOnly: true,
files: './app'
});
Adding localOnly
will remove any attempts to set the domain automagically in script tags or WebSocket addresses and instead will hard-code the correct localhost
address. This is exactly what is needed for use in electron.