Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump socket.io-parser and socket.io-client in /src/webrtc/samples/webrtccapturer/client #293

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Oct 28, 2022

Bumps socket.io-parser and socket.io-client. These dependencies needed to be updated together.
Updates socket.io-parser from 2.2.2 to 4.2.1

Release notes

Sourced from socket.io-parser's releases.

4.2.1

Bug Fixes

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

Links

4.2.0

Features

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

Links

4.1.2

Bug Fixes

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

Links

4.1.1

Links

4.1.0

Features

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

Links

4.0.5

Bug Fixes

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

Links

... (truncated)

Changelog

Sourced from socket.io-parser's changelog.

4.2.1 (2022-06-27)

Bug Fixes

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

4.2.0 (2022-04-17)

Features

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

4.1.2 (2022-02-17)

Bug Fixes

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

4.1.1 (2021-10-14)

4.1.0 (2021-10-11)

Features

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

4.0.4 (2021-01-15)

Bug Fixes

  • allow integers as event names (1c220dd)

4.0.3 (2021-01-05)

4.0.2 (2020-11-25)

... (truncated)

Commits
  • 5a2ccff chore(release): 4.2.1
  • b5d0cb7 fix: check the format of the index of each attachment
  • c7514b5 chore(release): 4.2.0
  • 931f152 chore: add Node.js 16 in the test matrix
  • 6c9cb27 chore: bump @​socket.io/component-emitter to version 3.1.0
  • b08bc1a feat: allow the usage of custom replacer and reviver (#112)
  • aed252c chore(release): 4.1.2
  • 89209fa chore: bump cached-path-relative from 1.0.2 to 1.1.0 (#113)
  • 0a3b556 chore: bump path-parse from 1.0.6 to 1.0.7 (#108)
  • 7f6b262 fix: allow objects with a null prototype in binary packets (#114)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by darrachequesne, a new releaser for socket.io-parser since your current version.


Updates socket.io-client from 2.0.4 to 4.5.3

Release notes

Sourced from socket.io-client's releases.

4.5.3

Bug Fixes

  • do not swallow user exceptions (2403b88)

Links:

Size of the bundles:

min min+gzip
socket.io.min.js 42.6 KB (-) 13.6 KB (-)
socket.io.msgpack.min.js 47.7 KB (-) 14.6 KB (-)
socket.io.esm.min.js 34.5 KB (-) 11.5 KB (-)

4.5.2

Bug Fixes

  • handle ill-formatted packet from server (c597023)

Links:

Size of the bundles:

min min+gzip
socket.io.min.js 42.6 KB (-) 13.6 KB (-)
socket.io.msgpack.min.js 47.7 KB (-) 14.6 KB (-)
socket.io.esm.min.js 34.5 KB (-) 11.5 KB (-)

4.5.1

There were some minor bug fixes on the server side, which mandate a client bump.

Links:

... (truncated)

Changelog

Sourced from socket.io-client's changelog.

4.5.3 (2022-10-15)

Bug Fixes

  • do not swallow user exceptions (2403b88)

4.5.2 (2022-09-02)

Bug Fixes

  • handle ill-formatted packet from server (c597023)

4.5.1 (2022-05-17)

There were some minor bug fixes on the server side, which mandate a client bump.

4.5.0 (2022-04-23)

Features

  • add details to the disconnect event (b862924)

The "disconnect" event will now include additional details to help debugging if anything has gone wrong.

Example when a payload is over the maxHttpBufferSize value in HTTP long-polling mode:

socket.on("disconnect", (reason, details) => {
  console.log(reason); // "transport error"
// in that case, details is an error object
console.log(details.message); "xhr post error"
console.log(details.description); // 413 (the HTTP status of the response)
// details.context refers to the XMLHttpRequest object
console.log(details.context.status); // 413
console.log(details.context.responseText); // ""
});

  • add support for catch-all listeners for outgoing packets (74e3e60)

... (truncated)

Commits
  • 2eca8da chore(release): 4.5.3
  • 7c05688 docs: add jsdoc for each public method
  • 2403b88 fix: do not swallow user exceptions
  • 1098618 ci: temporarily remove iOS 16 from the test matrix
  • 2d70813 chore(release): 4.5.2
  • c597023 fix: handle ill-formatted packet from server
  • 8c659bc chore: regenerate lockfile
  • f0350a0 chore(release): 4.5.1
  • abdba07 chore(release): 4.5.0
  • faf68a5 chore: update default label for bug reports
  • 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [socket.io-parser](https://github.com/socketio/socket.io-parser) and [socket.io-client](https://github.com/socketio/socket.io-client). These dependencies needed to be updated together.

Updates `socket.io-parser` from 2.2.2 to 4.2.1
- [Release notes](https://github.com/socketio/socket.io-parser/releases)
- [Changelog](https://github.com/socketio/socket.io-parser/blob/main/CHANGELOG.md)
- [Commits](socketio/socket.io-parser@2.2.2...4.2.1)

Updates `socket.io-client` from 2.0.4 to 4.5.3
- [Release notes](https://github.com/socketio/socket.io-client/releases)
- [Changelog](https://github.com/socketio/socket.io-client/blob/main/CHANGELOG.md)
- [Commits](socketio/socket.io-client@2.0.4...4.5.3)

---
updated-dependencies:
- dependency-name: socket.io-parser
  dependency-type: indirect
- dependency-name: socket.io-client
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Oct 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants