Add new transport: gRPC-Web
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 63.2k
- Forks
- 10.3k
- Avg merge
- 11d 20h
- Merged PRs (30d)
- 2
Description
Is your feature request related to a problem? Please describe.
There is a new standard called gRPC-Web that could be used as a transport between a client (browser) and backend service.
https://grpc.io/blog/postman-grpcweb/
It might be nice to have that as an alternative for Socket.IO when setting up the socket?
Describe the solution you'd like
Implement gRPC-Web
Describe alternatives you've considered
https://developer.mozilla.org/en-US/docs/Web/API/WebTransport is an alternative, but gRPC-Web might arguably be more performant. Leave the power to the user to decide what to use as transport.
Additional context
None
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
No source files, tests, or entry points are named. Start by reviewing the existing Socket.IO transport setup and the linked gRPC-Web material, then define how the transport would be selected by users; done should mean gRPC-Web works as an alternative transport without removing existing choices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, typescript
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100