Bump socket.io-parser from 4.2.1 to 4.2.3 in /packages/demo

[dependabot]

Bumps socket.io-parser from 4.2.1 to 4.2.3.

Release notes

Sourced from socket.io-parser's releases.

4.2.3

⚠️ This release contains an important security fix ⚠️

A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

TypeError: Cannot convert object to primitive value
       at Socket.emit (node:events:507:25)
       at .../node_modules/socket.io/lib/socket.js:531:14

Please upgrade as soon as possible.

Bug Fixes

• check the format of the event name (3b78117)

Links

• Diff: socketio/socket.io-parser@4.2.2...4.2.3

4.2.2

Bug Fixes

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

Links

• Diff: socketio/socket.io-parser@4.2.1...4.2.2

Changelog

Sourced from socket.io-parser's changelog.

4.2.3 (2023-05-22)

Bug Fixes

• check the format of the event name (3b78117)

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)

Commits

• b6c824f chore(release): 4.2.3
• dcc70d9 refactor: export typescript declarations for the commonjs build
• 3b78117 fix: check the format of the event name
• 0841bd5 chore: bump ua-parser-js from 1.0.32 to 1.0.33 (#121)
• 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)
• 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
web3-onboard-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 24, 2023 3:00am

[lnbc1QWFyb24]

@dependabot rebase

[dependabot]

Looks like this PR is already up-to-date with develop! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[lnbc1QWFyb24]

Hmmm the diff on the yarn.lock is huge. @Adamj1232 any thoughts or ideas on why that might be?

[Adamj1232]

Hmmm the diff on the yarn.lock is huge. @Adamj1232 any thoughts or ideas on why that might be?

It looks like it is installing the latest deps on the demo package and we dont (or atleast I don't) keep the demo package up to date as far as yarn -ing from within the package after updating dependencies. Mostly because when running the svelte demo (generally locally) yarn workspaces takes care of that.
When I run yarn within packages/demo it looks to create a pretty hefty and similar diff. I dont think it looks to be a problem but interesting to know 🤷🏼‍♂️