I built a framework for WebTransport in Go. Think routing, middleware, rooms, message framing — the stuff you get with Gin/Echo but for WebTransport instead of HTTP.
WebTransport gives you multiplexed streams and unreliable datagrams over QUIC. The existing Go library (quic-go/webtransport-go) handles the protocol, but you’re on your own for everything else. wt adds the framework layer.
What’s in it:
- Path routing with
{param}extraction - 50+ middleware (auth, rate limiting, CORS, compression, metrics, circuit breaker…)
- Rooms with pub/sub and presence
- Message framing (length-prefixed) so you don’t deal with raw byte streams
- Typed streams via generics
- Stream multiplexing (route different stream types on one connection)
- JSON-RPC over streams
- Go client SDK with auto-reconnect
- WebSocket fallback for browsers that don’t support WebTransport yet