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

@wptom/cms-sanity

v0.1.1

Published

Sanity CMS for WPTom templates: Studio schema, Astro loader and seeding, all generated from the template's content model. No dependencies besides @wptom/content-model.

Readme

@wptom/cms-sanity

Sanity as the content source for a WPTom template. Everything is generated from the template's content model (src/content/model.ts): the Studio schema with its validation rules and navigation, the Astro content loader and the seeding of the demo content. Pages don't change. Part of the WPTom integrations.

In a WPTom template:

pnpm cms sanity schema   # writes studio/schema.json for the template's Studio (studio/)
pnpm cms sanity seed     # uploads content and photos (SANITY_WRITE_TOKEN, Editor role)
CMS=sanity pnpm build    # builds the site from Sanity
  • sanitySchema(specs): document types and navigation as JSON. Required fields, patterns and ranges come from the model; images allow cropping; Markdown bodies use the markdown editor (sanity-plugin-markdown); single pages are pinned to one document each.
  • sanityContentLoader(...): reads published documents only (perspective=published), from the live API rather than the CDN, so a rebuild always sees what was just published. Images become CDN URLs (with the editor's crop) that Astro optimises like local files.
  • toSanityDocument(), uploadImage(), seedDocuments(), existingDocuments(): seeding. Document ids never contain a dot (Sanity keeps those private).

Content loads at build time: add a Sanity webhook (create, update, delete) that calls your host's deploy hook; pnpm cms sanity schema prints the filter. Requests are retried on rate limits. No dependencies besides @wptom/content-model. MIT License.