Why are we still using a 15-year-old WebSocket library?
​Don't get me wrong, the classic ws package is a legend. But it was built in a Node-only world. Today, we’re deploying to Cloudflare Workers, running servers on Bun, and testing in Deno. Fighting polyfills and native dependency errors just to get a socket connection open in 2026 is exhausting.
​So, I built a zero-dependency, runtime-agnostic alternative
@rabbx/ws