WebSocket Support Tracker
Open
Nobody has claimed this yet.
discussion
v2
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
Initial PR: https://github.com/unjs/nitro/pull/2170
Relavant docs:
Platform support
- Dev server
- Runtime handlers
- Dev handlers
-
bun - Cloudflare
-
cloudflare-pages -
cloudflare-module -
cloudflare(worker)
-
- Deno
-
deno-deploy -
deno-server
-
- Node
-
node-server -
nodeviawebsocketexport -
node-cluster
-
- Vercel
Needs investigation:
-
aws-lambda - AWS amplify
- Firebase
- Netlify
-
netlify-edge -
netlify-lambda
-
-
stormkit -
wnterjs -
zerabur
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the initial PR linked in the issue, then read the h3 WebSocket guide and crossws documentation. Review the unchecked platform targets, including dev handlers, node-cluster, AWS, Firebase, Netlify, Stormkit, wnterjs, and zerabur. Done means each target has an investigated and recorded support status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100