Opal-Estate-Pro

History

hatuhn f14a34ba19 uapte		2019-09-13 09:44:33 +07:00
..
certs	uapte	2019-09-13 09:44:33 +07:00
cli-options	uapte	2019-09-13 09:44:33 +07:00
dist	uapte	2019-09-13 09:44:33 +07:00
node_modules/fs-extra	uapte	2019-09-13 09:44:33 +07:00
templates	uapte	2019-09-13 09:44:33 +07:00
LICENSE	uapte	2019-09-13 09:44:33 +07:00
package.json	uapte	2019-09-13 09:44:33 +07:00
readme.md	uapte	2019-09-13 09:44:33 +07:00

readme.md

Keep multiple browsers & devices in sync when building websites.

Browsersync is developed and maintained internally at JH

Follow @Browsersync on twitter for news & updates.

Community

Features

Please visit browsersync.io for a full run-down of features

Requirements

Browsersync works by injecting an asynchronous script tag (<script async>...</script>) right after the <body> tag during initial request. In order for this to work properly the <body> tag must be present. Alternatively you can provide a custom rule for the snippet using snippetOptions

Upgrading from 1.x to 2.x ?

Providing you haven't accessed any internal properties, everything will just work as there are no breaking changes to the public API. Internally however, we now use an immutable data structure for storing/retrieving options. So whereas before you could access urls like this...

browserSync({server: true}, function(err, bs) {
    console.log(bs.options.urls.local);
});

... you now access them in the following way:

browserSync({server: true}, function(err, bs) {
    console.log(bs.options.getIn(["urls", "local"]));
});

Install and trouble shooting

browsersync.io docs

Integrations / recipes

Browsersync recipes

Support

If you've found Browser-sync useful and would like to contribute to its continued development & support, please feel free to send a donation of any size - it would be greatly appreciated!