Update browser-sync 2.26.14 → 2.29.3 (minor)

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ browser-sync (2.26.14 → 2.29.3) · Repo · Changelog

Release Notes

2.29.3

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

2.29.0

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

2.28.0

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

2.27.1

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

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 67 commits:

• v2.29.3
• fix: append to head if body not present yet - fixes #2031 (#2041)
• v2.29.2
• deps: drop qs (#2040)
• v2.29.1
• v2.29.1-alpha.0
• remove client deps
• v2.29.0
• fix: ie11 support (#2024)
• v2.28.3
• v2.28.2
• bump logger (#2026)
• chalk as main dep - fixes #2021 (#2025)
• v2.28.1
• fix(deps): loosen range on `ua-parser-js` - fixes #2009 (#2020)
• v2.28.0
• fix: remove document.write (#2019)
• browser-sync-2017 use chalk everywhere (#2018)
• v2.27.12
• build(deps): bump http-cache-semantics from 4.1.0 to 4.1.1 (#2011)
• build(deps): bump cookiejar in /packages/browser-sync (#2006)
• build(deps): bump cookiejar in /packages/browser-sync-ui (#2005)
• build(deps): bump parse-url and lerna (#2000)
• build(deps): bump minimist in /packages/browser-sync-ui (#1998)
• build(deps): bump minimist from 1.2.5 to 1.2.7 (#1997)
• build(deps): bump socket.io-parser in /packages/browser-sync-ui (#1996)
• build(deps): bump moment in /packages/browser-sync-ui (#1973)
• build(deps): bump ua-parser-js in /packages/browser-sync (#2007)
• v2.27.11
• updated deps (#1995)
• Add CodeSee architecture diagram workflow to repository (#1972)
• v2.27.10
• Updated portscanner to 2.2.0 (#1960)
• fix readme's
• Merge branch 'browser-sync-1946-esbuild'
• 👋 app veyor
• Merge pull request #1947
• drop webpack from UI
• build client with esbuild
• v2.27.9
• fix(cli): Where's the command help? fixes #1929 (#1945)
• v2.27.8
• more version bumps + github actions (#1940)
• Merge pull request #1936 from lachieh/socket-io-upgrade
• update browser-sync-client ts version
• restore test setting
• Upgrade to latest version of socket.io. Fixes #1847
• v2.27.7
• fixes #1916
• v2.27.6
• v2.27.5
• updated lockfile format
• Merge pull request #1915 from iwt-philipzeh/fix/ua-parser-version-security
• security-patches
• Merge pull request #1738 from davezuko/patch-1
• Merge pull request #1858 from arafalov/master
• v2.27.4
• security patches
• v2.27.3
• v2.27.2
• docs: added snippet option for website generation
• v2.27.1
• v2.27.0
• updated options
• feat: added option `snippet: boolean` - fixes #1882
• added failing test
• Fix #1799 - pesticide link

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)