Make ws a direct dependency#1163
Conversation
🦋 Changeset detectedLatest commit: 8beb207 The changes in this PR will be included in the next version bump. This PR includes changesets to release 43 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
BundleMonUnchanged files (136)
No change in files bundle size Final result: ✅ View report in BundleMon website ➡️ |
|
Documentation Preview: https://kit-docs-hbk20a8jw-anza-tech.vercel.app |
mcintyre94
left a comment
There was a problem hiding this comment.
Agreed with this change, I think it makes most sense as a direct dependency. I think you accidentally removed the typescript peer dependency though.
2abb466 to
eba8dbb
Compare
eba8dbb to
8beb207
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
|
🔎💬 Inkeep AI search and chat service is syncing content for source 'Solana Kit Docs' |
|
Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up. |

Problem
Currently, Node users must explicitly install
wsas a peer dependency to use RPC Subscription features. This creates onboarding friction as users need to understand what isws, which environment requires it and why it is required just to get started with Kit.Summary of Changes
This PR move
wsfrompeerDependenciestodependencies. Since the packages use conditional exports with separate entry points for Node and browser environments, browser builds will never includewsas the browser entry point simply doesn't import it.This means Node users get
wsout of the box while browser bundle sizes remain unaffected.