Skip to content
This repository has been archived by the owner on Jul 8, 2022. It is now read-only.

Bump socket.io-client from 4.4.1 to 4.5.1 #49

Merged
merged 1 commit into from
May 18, 2022

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 18, 2022

Bumps socket.io-client from 4.4.1 to 4.5.1.

Release notes

Sourced from socket.io-client's releases.

4.5.1

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

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.0

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)

This is similar to onAny(), but for outgoing packets.

Syntax:

socket.onAnyOutgoing((event, ...args) => {
  console.log(event);
</tr></table> 

... (truncated)

Changelog

Sourced from socket.io-client's changelog.

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)

This is similar to onAny(), but for outgoing packets.

Syntax:

socket.onAnyOutgoing((event, ...args) => {
  console.log(event);
});
  • slice write buffer according to the maxPayload value (46fdc2f)

The server will now include a "maxPayload" field in the handshake details, allowing the clients to decide how many packets they have to send to stay under the maxHttpBufferSize value.

Commits
  • f0350a0 chore(release): 4.5.1
  • abdba07 chore(release): 4.5.0
  • faf68a5 chore: update default label for bug reports
  • c0ba734 chore: add Node.js 16 in the test matrix
  • e859018 refactor: replace the disconnected attribute by a getter
  • 74e3e60 feat: add support for catch-all listeners for outgoing packets
  • 692d54e chore: point the CI badge towards the main branch
  • 6fdf3c9 refactor: import single-file 3rd party modules
  • b862924 feat: add details to the disconnect event
  • eaf782c docs: remove broken badges
  • See full diff in compare view

Dependabot compatibility score

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 dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels May 18, 2022
Bumps [socket.io-client](https://github.com/socketio/socket.io-client) from 4.4.1 to 4.5.1.
- [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@4.4.1...4.5.1)

---
updated-dependencies:
- dependency-name: socket.io-client
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/socket.io-client-4.5.1 branch from 168fffc to 609de9c Compare May 18, 2022 03:05
@Huskydog9988 Huskydog9988 merged commit c649424 into main May 18, 2022
@Huskydog9988 Huskydog9988 deleted the dependabot/npm_and_yarn/socket.io-client-4.5.1 branch May 18, 2022 03:08
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant