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

relay-backend

v0.0.3

Published

Bundled API testing UI for Node backends with endpoint statuses and Git collaboration.

Readme

Relay for Node

API testing on your backend's existing /relay route. The UI, themes and assets are bundled. No Python, repository clone, frontend build or CDN is required.

npm install relay-backend

Express

import express from 'express';
import { relay } from 'relay-backend';
import { openapi } from './generated-openapi.js';

const app = express();
const tester = relay({ openapi, enabled: process.env.NODE_ENV !== 'production' });
app.use(tester); // Before body parsers and catch-all handlers.
app.use(express.json());
// Register your API routes as usual.
const server = app.listen(3000);
server.on('close', () => void tester.close());

Open http://localhost:3000/relay. If your backend already serves /openapi.json, omit openapi. A provider such as openapi: () => generatedDocument supports regenerated schemas.

Fastify

import Fastify from 'fastify';
import swagger from '@fastify/swagger';
import { relayFastify } from 'relay-backend';

const app = Fastify();
await app.register(swagger, {
  openapi: { info: { title: 'My Portal', version: '1' } }
});
// Register your API routes with their schemas here.
await app.register(relayFastify, {
  enabled: process.env.NODE_ENV !== 'production'
});
await app.listen({ port: 3000 });

Fastify reads app.swagger() automatically. With another generator, pass its document using openapi. Application hooks still apply, so configure your authentication hooks to allow the local /relay tooling routes if they otherwise protect every path.

JavaScript and TypeScript

ES modules and CommonJS are supported, with bundled TypeScript declarations:

const { relay, relayFastify } = require('relay-backend');

Node 22.13 or newer is required. Express, Fastify and Node HTTP are the tested adapters. Route definitions and request schemas come from OpenAPI 3.0/3.1 JSON; Relay cannot infer TypeScript interfaces or undocumented Express routes. Other frameworks and runtimes need their own adapter verification.

Standalone

For a local backend that already exposes OpenAPI:

npx relay-backend --target http://127.0.0.1:3000

This opens a separate tester at http://127.0.0.1:4477/relay/. Native mounting uses the backend's existing port instead. A saved report opens with npx relay-backend open endpoint.relay.

Team statuses

Endpoints start as Done. Status changes are manual. Set syncStatus: true to share them automatically through your existing Git origin using a separate relay-status branch. Git identity attributes each status update; native Node handler authors are not currently inferred. Request bodies, tokens and responses are never stored in that branch. Keep Git credentials configured on each developer's machine. See the team guide.

Relay accepts loopback hosts and clients only and requires same-origin CSRF protection for tester actions. API execution runs real backend handlers. Multipart uploads, external/YAML references, browser OAuth and public hosting are outside this version's scope.

Detailed configuration: Node integration guide. Apache-2.0; bundled third-party licenses are included.