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

@cms0/cms0

v0.4.1

Published

Typed client + schema tooling for cms0.

Readme

@cms0/cms0

Typed client + schema tooling for cms0.

Install

pnpm add @cms0/cms0

Usage

import { cms0, toNextMetadata } from "@cms0/cms0";
import type { Metadata } from "next";
import type { Image, Seo } from "@cms0/cms0/custom-types";

type RootSchema = {
  homePage: {
    heroImage: Image;
    seo: Seo;
  };
};

export const data = cms0<RootSchema>({
  apiConfig: {
    baseUrl: import.meta.env.VITE_CMS0_API_BASEURL,
    key: import.meta.env.VITE_CMS0_API_KEY,
  },
});

const page = await data.homePage();
const metadata = toNextMetadata<Metadata>(page.seo, { locale: "en" });

VITE_CMS0_API_BASEURL should point at the content runtime root, for example http://localhost:3000/api/content for self-hosted or http://localhost:3001/api/content/stage for a website environment path.

Accessor Options

All root/model accessors accept options:

await data.homePage({
  includeId: true,
  locale: "en",
  fields: ["heroImage", "seo.openGraph.images"],
  exclude: ["seo.jsonLd"],
  graph: {
    pageSize: "full",
    paths: {
      "seo.openGraph.images": { pageSize: 50 },
    },
  },
  query: { raw: 1 },
});
  • fields: recursive include projection (supports nested paths like a.b.c).
  • exclude: recursive remove projection (also supports nested paths).
  • graph: resolved graph read controls. Global page, pageSize, orderBy, orderDir, and search apply recursively to graph-backed arrays. The SDK defaults graph pageSize to "full" for resolved root reads. Use graph.paths for dot-path overrides.
  • query: passthrough query params to API.

Custom Types

See CUSTOM_TYPES.md for the built-in custom types you can reference.