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

@plumile/relay

v0.2.14

Published

Shared Relay runtime helpers for Plumile applications

Readme

@plumile/relay

Shared Relay environment, transport, provider, and operation-activity helpers for Plumile applications.

HTTP authentication ownership

configureShortAccessTokenRelayEnvironment() injects an auth-aware GraphQL fetch into this package. The injected fetch owns the single refresh and retry after 401; this transport owns multipart encoding, timeouts, and retries for network, 408, 429, and 5xx failures. It does not patch globalThis.fetch.

getAuthHeaders(signal?) receives the same operation signal across HTTP retries. An error from this provider rejects the operation with the original error before sending any request, and is never retried as a network failure. The signal is omitted for WebSocket authentication. Existing callbacks without a parameter remain supported.

Relay query disposal aborts the active HTTP attempt and the complete retry lifecycle, including a pending backoff. Disposed operations never publish a late response or error to their observer.

WebSocket transport contract

Subscriptions use the graphql-transport-ws subprotocol through the package's owned client. The client deliberately remains local because the deployed server contract includes authentication rotation beyond the standard protocol:

  • the client sends connection_init with the current authentication headers and waits for connection_ack before subscribing;
  • subscriptions use subscribe, next, error, and complete, while keep-alive messages use ping and pong;
  • credential rotation sends connection_auth_update and requires connection_auth_update_ack within five seconds;
  • an unexpected disconnect retries with bounded exponential backoff (at most ten attempts) and re-subscribes every still-active operation after the next ack;
  • invalid or unsupported server messages close the socket with code 4400; normal environment disposal closes it with code 1000.

Do not replace this client with a generic GraphQL WebSocket dependency unless that implementation proves the same authentication-update and reconnection contract without an adapter of comparable complexity.

Validation

From the repository root, run the Relay tests and build:

npx vitest run packages/relay
npm run --workspace @plumile/relay build:package