chore(deps): update dependency browser-sync to v2.29.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
browser-sync (source)	2.26.14 → 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,
});

---

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.

[qlty-cloud-legacy]

The PR diff size of 5243 lines exceeds the maximum allowed for the inline comments feature.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @react-pdf/renderer@2.1.2
npm ERR! Found: react@18.1.0
npm ERR! node_modules/react
npm ERR!   dev react@"18.1.0" from the root project
npm ERR!   peer react@">=16.0.0" from @ant-design/icons@4.7.0
npm ERR!   node_modules/@ant-design/icons
npm ERR!     @ant-design/icons@"^4.0.0" from antd@4.0.1
npm ERR!     node_modules/antd
npm ERR!       antd@"^4.0.0" from the root project
npm ERR!   17 more (rc-util, antd, rc-align, rc-drawer, rc-dropdown, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.6 || ^17.0.0" from @react-pdf/renderer@2.1.2
npm ERR! node_modules/@react-pdf/renderer
npm ERR!   @react-pdf/renderer@"^2.1.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@17.0.2
npm ERR! node_modules/react
npm ERR!   peer react@"^16.8.6 || ^17.0.0" from @react-pdf/renderer@2.1.2
npm ERR!   node_modules/@react-pdf/renderer
npm ERR!     @react-pdf/renderer@"^2.1.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/a8e92b/405b6b/cache/others/npm/_logs/2023-05-28T10_33_24_644Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/a8e92b/405b6b/cache/others/npm/_logs/2023-05-28T10_33_24_644Z-debug-0.log

[qlty-cloud-legacy]

Code Climate has analyzed commit c7f6587 and detected 0 issues on this pull request.

View more on Code Climate.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @react-pdf/renderer@2.1.2
npm error Found: react@18.1.0
npm error node_modules/react
npm error   dev react@"18.1.0" from the root project
npm error   peer react@">=16.0.0" from @ant-design/icons@4.7.0
npm error   node_modules/@ant-design/icons
npm error     @ant-design/icons@"^4.0.0" from antd@4.0.1
npm error     node_modules/antd
npm error       antd@"^4.0.0" from the root project
npm error   17 more (rc-util, antd, rc-align, rc-drawer, rc-dropdown, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.6 || ^17.0.0" from @react-pdf/renderer@2.1.2
npm error node_modules/@react-pdf/renderer
npm error   @react-pdf/renderer@"^2.1.2" from the root project
npm error
npm error Conflicting peer dependency: react@17.0.2
npm error node_modules/react
npm error   peer react@"^16.8.6 || ^17.0.0" from @react-pdf/renderer@2.1.2
npm error   node_modules/@react-pdf/renderer
npm error     @react-pdf/renderer@"^2.1.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-08-14T18_33_09_356Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-14T18_33_09_356Z-debug-0.log