npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@spinajs/http-socket-common

v3.0.29

Published

Wire protocol shared by the spinajs WebSocket server and client: envelopes, error codes, protocol version and contract typing helpers

Readme

@spinajs/http-socket-common

The wire protocol shared by @spinajs/http-socket (server) and @spinajs/http-socket-client. It has no dependencies and runs in browsers and Node. Both packages re-export it, so apps rarely import it directly.

  • PROTOCOL_VERSION (1) and the wire event names WIRE_EVENTS:
    • commands: cmd
    • events in both directions: evt
    • stream frames, server to client: chunk, end, fail
    • client to server: credit, cancel
  • SYSTEM_EVENTS: sys.shutdown, sys.disconnect.
  • The envelopes (types):
    • Handshake
    • CommandRequest (id, name, payload, deadline, traceparent, and credits for streams)
    • CommandReply: CommandResultReply, CommandStreamReply or CommandErrorReply
    • EventFrame, ShutdownNotice, DisconnectNotice
    • the stream frames Chunk, StreamEnd, StreamFail, StreamCredit, and CancelFrame
  • Guards for them: isCommandRequest, isEventFrame, isCancelFrame, isChunk, isStreamEnd, isStreamFail, isStreamCredit.
  • Names and ids: isName / NAME_PATTERN / MAX_NAME_LENGTH and isId / ID_PATTERN / MAX_ID_LENGTH.
  • Keys: isKey / MAX_KEY_LENGTH (the rule for CommandRequest.idempotencyKey and after, which are reserved for durable commands).
  • The 13 error codes:
    • ErrorCode, ERROR_CODES, DEFAULT_RETRYABLE, isErrorCode
    • the wire shape SocketError and its guard isSocketError
    • SocketException, a throwable SocketError with toWire() / fromWire()
  • Typed contracts: defineContract<C>(), ContractShape, SocketContract and the helper types CommandName, CommandPayload, CommandResult, EventName, EventPayload, ClientEventName, ClientEventPayload, ContractOf.

Full documentation: docs/http-socket-common, covering the wire protocol, the handshake, frame guards, error codes, custom socket exceptions, typed contracts and the contract helper types.

See @spinajs/http-socket for the server, @spinajs/http-socket-client for the client and packages/http-socket-example for a runnable example.