Update dependency browser-sync to v2.29.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
browser-sync (source)	2.24.5 → 2.29.3

---

Release Notes

BrowserSync/browser-sync (browser-sync)

v2.29.3: The one that fixes snippetOptions

Compare Source

What's Changed

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

Full Changelog: BrowserSync/browser-sync@v2.29.2...v2.29.3

v2.29.2

Compare Source

v2.29.1

Compare Source

What's Changed

• trim-deps by @​shakyShane in #​2028

Full Changelog: BrowserSync/browser-sync@v2.29.0...v2.29.1

v2.29.0: The one that restores IE11 support 💪

Compare Source

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: BrowserSync/browser-sync@v2.28.3...v2.29.0

v2.28.3

Compare Source

v2.28.2

Compare Source

v2.28.1

Compare Source

v2.28.0: the one that finally removes document.write

Compare Source

What's Changed

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

Full Changelog: BrowserSync/browser-sync@v2.27.12...v2.28.0

v2.27.12

Compare Source

v2.27.11

Compare Source

v2.27.10

Compare Source

v2.27.9: 2.27.9

Compare Source

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: BrowserSync/browser-sync@v2.27.8...v2.27.9

v2.27.8: 2.27.8

Compare Source

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

v2.27.7

Compare Source

v2.27.6

Compare Source

v2.27.5

Compare Source

v2.27.4

Compare Source

v2.27.3

Compare Source

v2.27.1: added snippet: boolean option

Compare Source

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

v2.26.14: upgraded dependencies

Compare Source

This is a maintenance release to address 2 security related issues (socket.io & axios)

Happy Browsersync'in :)

v2.26.13

Compare Source

v2.26.12

Compare Source

v2.26.10

Compare Source

v2.26.9

Compare Source

v2.26.7

Compare Source

v2.26.6

Compare Source

v2.26.5

Compare Source

v2.26.4

Compare Source

v2.26.3: 2.26.0 -> 2.26.3

Compare Source

fixes

• application/wasm support - fixes #​1598 d60cd91
• deps - ensure previous users of browser-sync-client are not affected by new structure - fixes #​1615 0a2ff5a
• npm audit fixes across all packages - fixes #​1618 9f3fea4

v2.26.2

Compare Source

v2.26.1

Compare Source

v2.26.0

Compare Source

these notes describe the change from 2.24.6 -> 2.26.0

fixes

• Removing default logger prefix [BS] - fixes #​1607 257fba6
• case-insensitive matching on domain key in proxy responses dacfc8b
• bump chokidar fixing fsevents build - closes #​1613 11729cc
• Unexpected Page Reload after Pausing in Debugger - fixes #​1591 06ee1b7
• scroll - add missing init method for window.name method of scroll restoring - fixes #​1586 #​1457 #​1457 9e96603
• proxy Port gets unnecesarily rewritten in Proxy - fixes #​1577 48286e0

chore

• move cypress to top-level dep 0d4ab81
• package-lock files 900e23e
• change API of option transforms ef12e9a

lerna

• initial version 7c0ad4e
• more path updates c108af8
• updated more stuff since the move to lerna 4ac3a49
• bring in server/client/ui d6198f9
• add browser-sync-ui 325c775

feature

• adding 'listen' option to restrict binding of interfaces d641916

docs

• emphasize a couple of points - fixes #​1461 cf0febd
• added additional note about httpModule option - fixes #​1485 16487ad

deps

• npm audit for localtunnel - fixes #​1587 27f2173
• easy-extender@​2.3.4 cypress@​3.1.0 supertest@​3.1.0 a6578a3

v2.25.0: the listen option release

Compare Source

Browsersync can now be used in more restrictive areas, ones where you cannot simply bind to all addresses on the host (such as schools or universities) - this is enabled via the listen option.

For backwards compatibility reasons, we actually cannot use the host option to acheive this (even though that would make the most sense), as it would break some people's existing setups.

This is mainly because in the past, host was not used to determine an address to bind to, but rather just as a way of changing the urls Browsersync displays to the user. :( :( :(

It was a big mistake, but now with the sheer size of the user base we have, every tiny change to any existing option causes some kind of breakage. I'm not prepared to do that again with host.

So, instead we're back to the old method of instead adding a new option, that I've called listen. It's the only way we can acheive the goal without breaking existing users who are using host for other reasons.

The idea is that you'd only ever use the listen option if you want to restrict the address being bound to. For example, the following will serve files from the current directory, but behind the scenes Browsersync will only bind to localhost (this does mean that other features such as external urls will not work any more, but if you need this listen option in the first place, that will not be a concern for you)

npm i -g browser-sync@2.25.0
browser-sync . --listen localhost

v2.24.7: Bug fixes

Compare Source

fix

• Update opn to latest release b6ba0dd
• scroll - add missing init method for window.name method of scroll restoring - fixes #​1586 #​1457 #​1457 9e96603
• proxy Port gets unnecesarily rewritten in Proxy - fixes #​1577 48286e0

deps

• easy-extender@​2.3.4 cypress@​3.1.0 supertest@​3.1.0 a6578a3

v2.24.6

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.