v3.0.3

What's Changed

• remove xip by @shakyShane in #2065
• deps: send + micromatch by @shakyShane in #2088

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

v3.0.2

What's Changed

• fix: dist path by @bufo24 in #2054
• fix ui-external url by @qdirks in #1970

New Contributors

• @bufo24 made their first contribution in #2054
• @qdirks made their first contribution in #1970

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

v3.0.1

⚠️ Breaking

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

What's Changed

• build(deps): bump nanoid and mocha in /packages/browser-sync-ui by @dependabot in #2015
• build(deps): bump engine.io from 6.2.1 to 6.4.2 in /packages/browser-sync by @dependabot in #2038
• build(deps-dev): bump webpack from 5.75.0 to 5.76.0 in /packages/browser-sync-client by @dependabot in #2027
• build(deps): bump json5 from 1.0.1 to 1.0.2 by @dependabot in #2014
• build(deps): bump json-schema and jsprim in /packages/browser-sync-ui by @dependabot in #2042
• fixing nx caching, run tests on nonde 16, 18 & 20 by @shakyShane in #2050
• Update README.md by @shakyShane in #2051
• adding playwright tests by @shakyShane in #2052
• remove localtunnel by @shakyShane in #2059

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

The one that fixes snippetOptions

What's Changed

• fix: append to head if body not present yet - fixes #2031 by @shakyShane in #2041

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

v2.29.1

What's Changed

• trim-deps by @shakyShane in #2028

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

The one that restores IE11 support 💪

What's Changed

• fix ie11 by @shakyShane in #2024

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`

What's Changed

• browser-sync-2017 use chalk everywhere by @shakyShane in #2018
• fix: remove document.write by @shakyShane in #2019

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

2.27.9

What's Changed

• fix(cli): Where's the command help? fixes #1929 by @shakyShane in #1945

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

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

PR:

• 58ab4ab

Resolved Issues:

• #1850
• #1892
• #1925
• #1926
• #1933

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

added `snippet: boolean` option

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,
});