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

@papack/api

v1.1.2

Published

Minimal, opinionated HTTP API core for people who want full control over IO, parsing, streaming, and errors.

Readme

@papack/api

Minimal, opinionated HTTP API core for people who want full control over IO, parsing, streaming, and errors. No magic. No Hooks. No implicit parsing.

Context is explicitly extensible. You can attach schemas, business logic, services, or infrastructure once, and they are available on ctx in every handler, you dont need hooks.

Core Rules

  • Transport is dumb. handlers decide everything.
  • ctx.req.body is always string (if present).
  • Body is read exactly once by the core.
  • Parsing is never automatic.
  • Streaming stays streaming.

Context

  • App context is injected once
  • Available in all handlers
  • No mutation rules enforced
const api = new Api({ value: "from-context" });

Design Intent

  • Zero hidden transformations
  • Predictable transport semantics
  • Streaming stays streaming
  • Parsing is a user decision

RPC

  • POST only
  • req is the API surface
  • Return value will be strinifyed with JSON.stringify
server.rpc("/rpc", (ctx) => {
  return {
    raw: ctx.req.body,
    value: ctx.value,
  };
});

SSE

  • GET only
  • Real text/event-stream
  • Explicit emit()
  • Guaranteed onCleanup() on disconnect
server.sse<{ tick: number }>("/events", (ctx) => {
  let i = 0;
  const id = setInterval(() => {
    ctx.emit("tick", i++);
  }, 1000);

  ctx.onCleanup(() => {
    clearInterval(id);
  });
});

Blob (raw by design)

  • Return Buffer | Readable
  • No headers added
  • No Content-Type guessing
  • Streams use Transfer-Encoding: chunked
  • Full backpressure control
server.blob("/file", () => {
  return fs.createReadStream("./big.bin");
});

Upload

  • POST only
  • Request body is binary
  • ctx.req is a Readable
  • Core does not read or buffer
  • No ctx.req.body
  • No multipart assumptions
server.upload("/upload", async (ctx) => {
  for await (const chunk of ctx.req) {
    // stream processing
  }

  return "OK";
});

CORS

CORS is handled centrally by the core when enabled at instantiation. If configured, the server:

  • sets Access-Control-Allow-Origin to a concrete origin
  • enables Access-Control-Allow-Credentials for session cookies
  • responds to OPTIONS preflight requests with 204
const api = new Api(ctx, {
  cors: {
    origin: "http://localhost:5173",
  },
});

Errors

  • Explicit HttpErrors only
  • Status code + stable "ERROR_CODE"
  • No messages
  • No leaking

Examples:

"NOT_FOUND"
"METHOD_NOT_ALLOWED"
"BAD_REQUEST"