React_Client_App_Access

rpm-mcarman b9f7ec4306 First Commit		il y a 3 ans
..
certs	First Commit	il y a 3 ans
cli-options	First Commit	il y a 3 ans
dist	First Commit	il y a 3 ans
node_modules	First Commit	il y a 3 ans
templates	First Commit	il y a 3 ans
LICENSE	First Commit	il y a 3 ans
package.json	First Commit	il y a 3 ans
readme.md	First Commit	il y a 3 ans

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!