-
Notifications
You must be signed in to change notification settings - Fork 3.4k
fix(deps): update dependency socket.io-parser to v4.2.3 [security] #32542
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
base: develop
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -28,7 +28,7 @@ | |
| "flatted": "3.2.9", | ||
| "socket.io": "4.0.1", | ||
| "socket.io-client": "4.0.1", | ||
| "socket.io-parser": "4.0.5", | ||
| "socket.io-parser": "4.2.3", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bug: Socket.io Version Mismatch Causes Runtime IssuesThe There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bug: Socket.IO Parser Upgrade Causes Emitter ConflictThe There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bug: Patch mismatch blocks circular object serialization upgradeThe socket.io-parser dependency is being upgraded from 4.0.5 to 4.2.3, but there's an existing patch file (packages/socket/patches/socket.io-parser+4.0.5.patch) that will no longer be applied. The patch-package tool requires exact version matches in the filename. This patch adds critical functionality for handling circular objects in socket.io messages using the flatted library and WeakMap tracking. Without this patch being applied to version 4.2.3, the application will lose the ability to properly serialize circular objects, potentially causing runtime errors or data corruption. A new patch file named socket.io-parser+4.2.3.patch needs to be created, or the existing patch needs to be verified as no longer necessary for version 4.2.3. |
||
| "uuid": "8.3.2" | ||
| }, | ||
| "devDependencies": { | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7690,6 +7690,11 @@ | |
| "@smithy/types" "^2.8.0" | ||
| tslib "^2.5.0" | ||
|
|
||
| "@socket.io/component-emitter@~3.1.0": | ||
| version "3.1.2" | ||
| resolved "https://registry.yarnpkg.com/@socket.io/component-emitter/-/component-emitter-3.1.2.tgz#821f8442f4175d8f0467b9daf26e3a18e2d02af2" | ||
| integrity sha512-9BCxFwvbGg/RsZK9tjXd8s4UcwR0MWeFQ1XEKIQVVvAGJyINdrqKMcTRyLoK8Rse1GjzLV9cwjWV1olXRWEXVA== | ||
|
|
||
| "@stroncium/procfs@^1.2.1": | ||
| version "1.2.1" | ||
| resolved "https://registry.yarnpkg.com/@stroncium/procfs/-/procfs-1.2.1.tgz#6b9be6fd20fb0a4c20e99a8695e083c699bb2b45" | ||
|
|
@@ -29722,13 +29727,12 @@ [email protected]: | |
| parseuri "0.0.6" | ||
| socket.io-parser "~4.0.4" | ||
|
|
||
| socket.io-parser@4.0.5, socket.io-parser@~4.0.3, socket.io-parser@~4.0.4: | ||
| version "4.0.5" | ||
| resolved "https://registry.yarnpkg.com/socket.io-parser/-/socket.io-parser-4.0.5.tgz#cb404382c32324cc962f27f3a44058cf6e0552df" | ||
| integrity sha512-sNjbT9dX63nqUFIOv95tTVm6elyIU4RvB1m8dOeZt+IgWwcWklFDOdmGcfo3zSiRsnR/3pJkjY5lfoGqEe4Eig== | ||
| socket.io-parser@4.2.3, socket.io-parser@~4.0.3, socket.io-parser@~4.0.4: | ||
| version "4.2.3" | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bug: Parser Update Causes Socket.IO Compatibility IssuesUpdating Additional Locations (1) |
||
| resolved "https://registry.yarnpkg.com/socket.io-parser/-/socket.io-parser-4.2.3.tgz#926bcc6658e2ae0883dc9dee69acbdc76e4e3667" | ||
| integrity sha512-JMafRntWVO2DCJimKsRTh/wnqVvO4hrfwOqtO7f+uzwsQMuxO6VwImtYxaQ+ieoyshWOTJyV0fA21lccEXRPpQ== | ||
| dependencies: | ||
| "@types/component-emitter" "^1.2.10" | ||
| component-emitter "~1.3.0" | ||
| "@socket.io/component-emitter" "~3.1.0" | ||
| debug "~4.3.1" | ||
|
|
||
| [email protected]: | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Yarn Resolution Causes Socket.IO Parser Mismatch
The
yarnresolution forcessocket.io-parserto4.2.3, but[email protected]is still in use. This creates a version mismatch, as[email protected]expects an older parser (~4.0.3or~4.0.4). The newer parser has API changes, like thecomponent-emitterdependency structure, which[email protected]isn't compatible with, potentially causing runtime issues.