Create `nodejs/socket` repository for Node.js implementation of Cloudflare's Socket API
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
👋 I've been working on a Node.js implementation of Cloudflare's Socket API (https://developers.cloudflare.com/workers/runtime-apis/tcp-sockets/). Additionally, I've been working on the spec itself for that API; which is now a WinterCG workstream (https://github.com/wintercg/proposal-sockets-api).
I'd love to not have to own this myself, and would instead be happy to have it live in Node.js plus be published as @nodejs/socket.
What do folks think?
My implementation currently lives here: https://github.com/Ethan-Arrowood/socket and I'll be publishing it to @arrowood.dev/socket soon for early testing.
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 by reviewing the linked Cloudflare Socket API documentation, the WinterCG proposal-sockets-api workstream, and the current implementation in Ethan-Arrowood/socket. Determine whether the Node.js project should adopt the implementation and publish it as @nodejs/socket; done means the repository ownership and publishing decision are documented and the next steps are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100