Skip to content

Releases: BrowserSync/browser-sync

v3.0.3

24 Sep 16:17
Compare
Choose a tag to compare

What's Changed

Full Changelog: v3.0.2...v3.0.3

v3.0.2

27 Dec 20:52
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.0.1...v3.0.2

v3.0.1

27 Dec 20:08
Compare
Choose a tag to compare

⚠️ Breaking

  • removed localtunnel (it's not maintained, and was always optional) - see #2059

What's Changed

Full Changelog: v2.29.3...v3.0.1

The one that fixes snippetOptions

17 May 18:48
Compare
Choose a tag to compare

What's Changed

Full Changelog: v2.29.2...v2.29.3

v2.29.1

17 May 22:14
Compare
Choose a tag to compare

What's Changed

Full Changelog: v2.29.0...v2.29.1

The one that restores IE11 support 💪

16 Mar 20:30
Compare
Choose a tag to compare

What's Changed

esbuild does not support down-level transpiling as far as IE11 - so when I switched to it, it accidentally broke IE11 support 😢

This is an important issue for me - many devs that support old browsers like IE11 are doing so because their projects are used in public services, or internal applications. Not every developer out there has the luxury of supporting evergreen-only browsers.

So, IE11 will work once again 🎉. Please use the issues thread to make me aware of any problem that's preventing you from using Browsersync in your day job 💪 (and be sure to thumbs-up the issues you want to see resolved)

# IE11 works, again
npm install browser-sync@latest

Full Changelog: v2.28.3...v2.29.0

the one that finally removes `document.write`

27 Feb 22:34
Compare
Choose a tag to compare

What's Changed

Full Changelog: v2.27.12...v2.28.0

2.27.9

15 Mar 09:00
Compare
Choose a tag to compare

What's Changed

A bug prevented the help output from displaying - it was introduced when the CLI parser yargs was updated, and is now fixed :)

Full Changelog: v2.27.8...v2.27.9

2.27.8

13 Mar 21:31
Compare
Choose a tag to compare

This release upgrades Socket.io (client+server) to the latest versions - solving the following issues, and silencing security warning :)

PR:

Resolved Issues:

Thanks to @lachieh for the original PR, which helped me land this fix

added `snippet: boolean` option

24 Jun 17:00
Compare
Choose a tag to compare

This release adds a feature to address #1882

Sometimes you don't want Browsersync to auto-inject it's connection snippet into your HTML - now you can disable it globally via either a CLI param or the new snippet option :)

browser-sync . --no-snippet

or in any Browsersync configuration

const config = {
  snippet: false,
};

the original request was related to Eleventy usage, so here's how that would look

eleventyConfig.setBrowserSyncConfig({
  snippet: false,
});