Skip to content

BrowserSync/browser-sync

Folders and files

NameName
Last commit message
Last commit date

Latest commit

author
Shane Osbourne
Sep 24, 2024
1359821 · Sep 24, 2024
Sep 10, 2023
Sep 9, 2023
Sep 23, 2024
Sep 9, 2023
Mar 15, 2022
Nov 14, 2014
Sep 9, 2023
Jan 23, 2021
Sep 17, 2018
Feb 18, 2016
May 26, 2015
Dec 27, 2023
Jan 1, 2018
Sep 23, 2024
Sep 9, 2023
Apr 7, 2024
Apr 7, 2024
Sep 9, 2023

Repository files navigation

Keep multiple browsers & devices in sync when building websites.

Follow @Browsersync on twitter for news & updates.

Ask questions on Discord

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!

Support via PayPal

Supported by

Originally supported by JH - they provided financial support as well as access to a professional designer to help with Branding.

Apache 2 Copyright (c) 2021 Shane Osbourne