-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
feat: native support for Websockets #12973
base: main
Are you sure you want to change the base?
Conversation
…ionality for different handlers at different URLs, added example use cases to options-2 test app, added upgrade function for supporting additional adapters, and much more.
|
preview: https://svelte-dev-git-preview-kit-12973-svelte.vercel.app/ this is an automated message |
@LukeHagar LMK, if you need any help with this (you can reach me also on discord |
I have fully tested the node adapter and WS functionality through local builds. |
"polka": "^1.0.0-next.28", | ||
"sirv": "^3.0.0", | ||
"typescript": "^5.3.3", | ||
"typescript": "^5.7.3", |
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.
typescript was bumped to 5.7 because that's what unjs/crossws is using and it uses a generic version of UInt8Array that's only available in version 5.7
@@ -45,10 +45,11 @@ | |||
"@polka/url": "^1.0.0-next.28", | |||
"@sveltejs/kit": "workspace:^", | |||
"@sveltejs/vite-plugin-svelte": "^5.0.1", | |||
"@types/node": "^18.19.48", | |||
"@types/node": "^20.17.16", |
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.
Bumping node types from 18 to 20 seems to fix some rollup/vite types issue because that's what they're using as well I think.
This PR is a replacement to #12961 with a completely different Websocket implementation using
crossws
that should be fully compatible with all major runtimes.Functionality has been validated locally using basic tests in the
options-2
test app.Here is the new usage experience.
+server.js
The newest implementation allows different sets of handlers to be implemented on a per-route basis. I have tested some basic uses of websockets locally to much success.
This PR is intended to:
Resolve #12358
Resolve #1491
Steps left
+server
exports validationPlease don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpm changeset
and following the prompts. Changesets that add features should beminor
and those that fix bugs should bepatch
. Please prefix changeset messages withfeat:
,fix:
, orchore:
.Edits