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

@viktorbarzin/runtime

v0.1.0

Published

Process plumbing for Bun apps: process singletons, idle timeouts, request drain, graceful shutdown, the /api error envelope and zod body validation.

Readme

@viktorbarzin/runtime

Process-level plumbing for a Bun web app. Framework-free: every function takes a Request or returns a Response, and the app wires it into its middleware and routes.

import { z } from "zod";
import {
	ApiError, createErrorResponder, extendIdleTimeout, healthResponse,
	installShutdown, readJson, trackRequest, withFrameDenial,
} from "@viktorbarzin/runtime";

// once, at boot
installShutdown({
	beforeDrain: [{ name: "realtime", run: () => realtime.stop() }],
	afterDrain: [{ name: "pool", run: () => pool.close() }],
});

// in a route
const body = await readJson(request, z.object({ title: z.string().min(1) })); // 422 validation_error on failure
throw new ApiError(409, "conflict", "already there");

| Export | | |---|---| | processSingleton(key, create) | one value per process on globalThis[Symbol.for("@viktorbarzin:<key>")], for servers bundled twice | | extendIdleTimeout(request, s = 120), keepRequestOpen(request) | Bun's per-request idle timeout (default 10 s) raised, or lifted for a stream; false off Bun | | trackRequest(), requestsInFlight(), waitForDrain(ms) | in-flight accounting for graceful shutdown | | shutdown(signal, opts), installShutdown(opts) | beforeDrain steps, wait for in-flight requests (drainMs, default 5000), afterDrain steps, exit 0; a failing step is logged and the rest still run | | ApiError, errorResponse, createErrorResponder({ mappers, logger }) | the {"error": {"code", "message"}} envelope; app-specific errors map through mappers; anything else is logged and answered 500 internal_error | | readJson(request, schema), readQuery(request, schema), validationMessage | zod validation; failures name fields, never values | | noContent(), healthResponse() | 204; {"status":"ok"} | | FRAME_DENY_HEADERS, withFrameDenial(response) | frame-ancestors 'none' and X-Frame-Options: DENY, keeping a policy the route set |

Peers: @viktorbarzin/log, zod ^4.6.