Bump socket.io-parser and browser-sync

[dependabot[bot]]

Bumps socket.io-parser to 4.2.2 and updates ancestor dependency browser-sync. These dependencies need to be updated together.

Updates socket.io-parser from 3.2.0 to 4.2.2

Release notes

Sourced from socket.io-parser's releases.

4.2.2

Bug Fixes

• calling destroy() should clear all internal state (22c42e3)
• do not modify the input packet upon encoding (ae8dd88)

Links

• Diff: https://github.com/socketio/socket.io-parser/compare/4.2.1...4.2.2

4.2.1

Bug Fixes

• check the format of the index of each attachment (b5d0cb7)

Links

• Diff: https://github.com/socketio/socket.io-parser/compare/4.2.0...4.2.1

4.2.0

Features

• allow the usage of custom replacer and reviver (#112) (b08bc1a)

Links

• Diff: https://github.com/socketio/socket.io-parser/compare/4.1.2...4.2.0

4.1.2

Bug Fixes

• allow objects with a null prototype in binary packets (#114) (7f6b262)

Links

• Diff: https://github.com/socketio/socket.io-parser/compare/4.1.1...4.1.2

4.1.1

Links

• Diff: https://github.com/socketio/socket.io-parser/compare/4.1.0...4.1.1

4.1.0

Features

• provide an ESM build with and without debug (388c616)

Links

... (truncated)

Changelog

Sourced from socket.io-parser's changelog.

4.2.2 (2023-01-19)

Bug Fixes

• calling destroy() should clear all internal state (22c42e3)
• do not modify the input packet upon encoding (ae8dd88)

3.3.3 (2022-11-09)

Bug Fixes

• check the format of the index of each attachment (fb21e42)

3.4.2 (2022-11-09)

Bug Fixes

• check the format of the index of each attachment (04d23ce)

4.2.1 (2022-06-27)

Bug Fixes

• check the format of the index of each attachment (b5d0cb7)

4.0.5 (2022-06-27)

Bug Fixes

• check the format of the index of each attachment (b559f05)

4.2.0 (2022-04-17)

Features

... (truncated)

Commits

• 28dd668 chore(release): 4.2.2
• 22c42e3 fix: calling destroy() should clear all internal state
• ae8dd88 fix: do not modify the input packet upon encoding
• 9143aa4 chore: update browserslist
• 194a9b7 ci: migrate from zuul to webdriver.io
• a9758da ci: update actions in GitHub Actions workflows (#117)
• f0af883 docs: add missing versions in the changelog
• 5a2ccff chore(release): 4.2.1
• b5d0cb7 fix: check the format of the index of each attachment
• c7514b5 chore(release): 4.2.0
• Additional commits viewable in compare view

Updates browser-sync from 2.26.7 to 2.29.1

Release notes

Sourced from browser-sync's releases.

The one that restores IE11 support 💪

What's Changed

• fix ie11 by @​shakyShane in BrowserSync/browser-sync#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: https://github.com/BrowserSync/browser-sync/compare/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 BrowserSync/browser-sync#2018
• fix: remove document.write by @​shakyShane in BrowserSync/browser-sync#2019

Full Changelog: https://github.com/BrowserSync/browser-sync/compare/v2.27.12...v2.28.0

2.27.9

What's Changed

• fix(cli): Where's the command help? fixes #1929 by @​shakyShane in BrowserSync/browser-sync#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: https://github.com/BrowserSync/browser-sync/compare/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:

• https://github.com/BrowserSync/browser-sync/commit/58ab4ab861d7c50b4349f25bdd4c7f8871d0ad32

Resolved Issues:

• BrowserSync/browser-sync#1850
• BrowserSync/browser-sync#1892
• BrowserSync/browser-sync#1925
• BrowserSync/browser-sync#1926
• BrowserSync/browser-sync#1933

... (truncated)

Commits

• 6ffc212 v2.29.1
• 7b07798 v2.29.1-alpha.0
• 497f216 remove client deps
• bed04d4 v2.29.0
• 87421b5 fix: ie11 support (#2024)
• 59eb01a v2.28.3
• 3fd2720 v2.28.2
• 8487a85 bump logger (#2026)
• a841795 chalk as main dep - fixes #2021 (#2025)
• 9ea395f v2.28.1
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.