Skip to content

Replace websocket with ws to eliminate es5-ext dependency#633

Draft
jiridanek wants to merge 1 commit intomicrosoft:mainfrom
jiridanek:fix/replace-websocket-with-ws
Draft

Replace websocket with ws to eliminate es5-ext dependency#633
jiridanek wants to merge 1 commit intomicrosoft:mainfrom
jiridanek:fix/replace-websocket-with-ws

Conversation

@jiridanek
Copy link
Copy Markdown

Summary

The websocket package (theturtle32/WebSocket-Node) depends on es5-ext, which is quarantined by Nexus Firewall (sonatype-2022-2248). The websocket package has an open PR to drop es5-ext but it has been unreviewed for 9 months.

This PR proposes replacing websocket@^1.0.28 with ws@^8.18.0, the modern, actively maintained WebSocket implementation for Node.js (86M weekly downloads, zero es5-ext dependency).

Note: This is a draft to start the conversation. The ws package has a different API surface from websocket, so source code changes in the connections module would be needed. The immediate fix is in the companion PR that removes the direct es5-ext dep and adds an npm override.

Ref: #420

References

Made with Cursor

The websocket package (theturtle32/WebSocket-Node) depends on
es5-ext, which is quarantined. ws is the modern, actively maintained
alternative with 86M weekly downloads and zero es5-ext dependency.

This is a draft to start the conversation about the longer-term fix.
Source code changes to adapt to the ws API are needed.

Ref: microsoft#420
Co-authored-by: Cursor <cursoragent@cursor.com>
@jiridanek
Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree company="Red Hat"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant