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

@paperboycms/client

v0.4.0

Published

Typed client for the Paperboy headless CMS Delivery API — lists, search, media variants, render helpers, optional ETag cache. Zero dependencies, no codegen.

Readme

@paperboycms/client

The typed Delivery API client. Thin, dependency-free (besides the shared types), end-to-end typed from the same Zod schemas the server serializes with — no codegen step.

import { createClient } from "@paperboycms/client";

const cms = createClient({
  baseUrl: "https://cms.example.com",
  key: process.env.PAPERBOY_PUBLIC_KEY!, // pk_live_… = published only; prv_… = drafts (server-side!)
});

// One item (typed data via the generic)
type BlogPost = { title: string; body: string; publishDate?: string };
const post = await cms.getBySlug<BlogPost>("hello-world", { locale: "en", populate: 2 });

// Lists: pagination, sorting, field filters — `total` ignores pagination
const { items, total } = await cms.list<BlogPost>("BlogPost", {
  sort: "-data.publishDate",
  limit: 10,
  filter: { author: "Jane" },
});

// Full-text search (same no-leak chokepoint as everything else)
const hits = await cms.search("local ai", { type: "BlogPost", limit: 5 });

// Hierarchical URLs, the start page, globals
await cms.getByPath("/blog/hello-world");
await cms.startPage({ populate: 2 });
await cms.global("SiteSettings");

// Responsive images via the server's variant pipeline. An image field is
// delivered as an OBJECT ({ url, alt, … }), not a bare string — pass its `url`.
import { mediaUrl, mediaSrcset } from "@paperboycms/client";
const image = post!.data.image as { url: string; alt: string } | null;
const src = image && mediaUrl(image.url, { w: 640, format: "webp" });
const srcset = image && mediaSrcset(image.url); // 320/640/1024/1600w webp

Behavior

  • 404 → null on the singular getters; everything else non-OK throws a typed PaperboyError { status, message, body } (401 messages name the key problem explicitly).
  • etagCache: true opts into in-memory conditional GETs: the client replays each URL's ETag and serves 304s from its cache — free bandwidth wins for hot published content.
  • fetchInit merges into every request — e.g. Next.js needs { cache: "no-store" } for draft-mode freshness (see apps/web/app/lib/delivery.ts, which is this client in production shape).
  • Preview keys see drafts. Never ship one to a browser.

Rendering & SEO helpers

The client also ships schema-driven render helpers so a frontend switches on the declared field type instead of sniffing values:

import {
  renderRichText, isRichTextDoc,   // TipTap JSON → sanitized HTML (XSS-safe)
  contentAreas, blockData,         // iterate a content area's blocks
  renderKind,                      // map a field to a render kind via fieldTypes
  pbAreaAttrs,                     // data-pb-* attrs for the on-page-editing bridge
} from "@paperboycms/client";

const post = await cms.getByPath("/blog/hello");
// Every delivery item carries `fieldTypes` (declared type per public field) so an
// empty richtext field still renders as richtext, never as "". PASS IT to
// contentAreas: areas are then identified by SCHEMA, so an area named anything —
// and an area that is currently empty — is still found.
for (const area of contentAreas(post!.data, post!.fieldTypes)) {
  for (const block of area.blocks) {
    const data = blockData(block); // shared vs inline, normalized
  }
}
const html = renderRichText(post!.data.intro); // safe to set via innerHTML

SEO

Every PAGE item carries a server-computed seo block (DeliverySeo): normalized meta/canonical/robots, Open Graph + Twitter, per-@type JSON-LD, and breadcrumbs — computed post-sanitize (private fields can't leak), with preview always noindex.

import type { DeliverySeo } from "@paperboycms/client";
const seo = post!.seo; // null on non-page kinds
// URLs in `seo` are relative — absolutize against your site origin before emitting.

Preview tokens (server-side)

Rendering drafts means deciding, per request, whether the caller is allowed to see them. The admin never puts PREVIEW_SECRET in a browser: it asks its own API for a signed, minutes-long token and passes it to your frontend as ?pbt=. Verify it with the subpath export:

import { verifyPreviewToken, constantTimeEqual } from "@paperboycms/client/preview-token";

const preview =
  // ?pbt= — the short-lived token the in-editor preview iframe sends.
  (await verifyPreviewToken(process.env.PREVIEW_SECRET!, url.searchParams.get("pbt"))) ||
  // ?pb= — the long-lived secret, for server-side callers that legitimately hold it.
  constantTimeEqual(url.searchParams.get("pb") ?? "", process.env.PREVIEW_SECRET!);

const cms = createClient({
  baseUrl: process.env.PAPERBOY_API_URL!,
  key: preview ? process.env.PAPERBOY_PREVIEW_KEY! : process.env.PAPERBOY_PUBLIC_KEY!,
});

PREVIEW_SECRET must be byte-identical to the API's. Notes:

  • It's a separate subpath on purpose. Its first argument is your secret, so it must never be reachable from a browser bundle — importing it from @paperboycms/client is deliberately impossible.
  • WebCrypto, so it runs anywhere — Node, Cloudflare Workers, Deno, Bun. That's why it's async: Workers has no synchronous HMAC.
  • It fails closed: malformed tokens, a tampered or absent MAC, an expired expiry, and an unset secret all return false. The MAC is checked before the expiry, so a forged token can't be used to probe expiry behaviour.
  • If your PREVIEW_SECRET still falls back to a committed dev default, guard that in production yourself — see apps/web/app/lib/preview.ts in the Paperboy repo.