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.

Sign up for GitHub

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

Jump to bottom

[Snyk] Upgrade socket.io from 2.0.4 to 2.3.0 #2

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

[Snyk] Upgrade socket.io from 2.0.4 to 2.3.0 #2

wants to merge 1 commit into from

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade socket.io from 2.0.4 to 2.3.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
  • The recommended version is 4 versions ahead of your current version.
  • The recommended version was released 3 months ago, on 2019-09-20.
Release notes
Package name: socket.io
  • 2.3.0 - 2019-09-20

    Diff: 2.2.0...2.3.0

  • 2.2.0 - 2018-11-28

    Features

    • add cache-control header when serving the client source (#2907)

    Bug fixes

    • throw an error when trying to access the clients of a dynamic namespace (#3355)

    Milestone: 2.2.0
    Diff: 2.1.1...2.2.0
    Client release: 2.2.0
    Diff engine.io: socketio/engine.io@3.2.0...3.3.1
    Diff ws: https://github.com/websockets/ws/compare/3.3.1..6.1.2

  • 2.1.1 - 2018-05-17

    Features

    (server) add local flag to the socket object (#3219)

    socket.local.to('room101').emit(/* */);

    Bug fixes

    (client) fire an error event on middleware failure for non-root namespace (socketio/socket.io-client#1202)

    Milestone: 2.1.1
    Diff: 2.1.0...2.1.1 (client diff)

  • 2.1.0 - 2018-03-29

    Features

    • add a 'binary' flag (#3185)
    // by default, the object is recursively scanned to check whether it contains some binary data
// in the following example, the check is skipped in order to improve performance
socket.binary(false).emit('plain-object', object);

    // it also works at the namespace level
    
io.binary(false).emit('plain-object', object);

    • add support for dynamic namespaces (#3195)
    io.of(/^\/dynamic-\d+$/).on('connect', (socket) => {
  // socket.nsp.name = '/dynamic-101'
});

    // client-side
    
const client = require('socket.io-client')('/dynamic-101');

    Bug fixes

    • properly emit 'connect' when using a custom namespace (#3197)
    • include the protocol in the origins check (#3198)

    Important note ⚠️ from Engine.IO 3.2.0 release

    There are two non-breaking changes that are somehow quite important:

    • ws was reverted as the default wsEngine (socketio/engine.io#550), as there was several blocking issues with uws. You can still use uws by running npm install uws --save in your project and using the wsEngine option:
    var engine = require('engine.io');
var server = engine.listen(3000, {
  wsEngine: 'uws'
});

    Milestone: 2.1.0
    Diff: 2.0.4...2.1.0
    Engine.IO version: 3.2.x

  • 2.0.4 - 2017-10-22

    Bug fixes

    • do not throw when receiving an unhandled error packet (#3038)
    • reset rooms object before broadcasting from namespace (#3039)

    Milestone: 2.0.4
    Diff: 2.0.3...2.0.4

from socket.io GitHub release notes
Commit messages
Package name: socket.io

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@snyk-bot