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

create-substrat

v0.7.0

Published

Scaffold a Substrat vertical — `npm create substrat <dir>`.

Readme

create-substrat

Scaffold a Substrat vertical.

npm create substrat <dir>
npm create substrat .        # scaffold into the current directory

Full documentation: https://substrat.net/reference/create-substrat

What you get

A project that installs and runs, plus an instruction layer so your AI editor already knows the rules and the build flow:

  • src/manifest.ts, migrations.ts, module.ts, provision.ts, seed.ts, a Node server.ts for local work, and a worker.ts that mounts the platform surface via @substrat-run/vertical-host.
  • test/scenario.test.ts — the scenario test the build flow grows.
  • AGENTS.md + .substrat/playbook.md — the rules and the build flow, read by Claude Code, Cursor, and opencode alike; each gets its own command stub.
  • Generated package.json, tsconfig.json, vitest.config.ts, .gitignore, README.md, including the substrat block that substrat push reads — so you never author wrangler config.

The scaffolder writes the skeleton; the agent writes the vertical, guided by the playbook.

cd <dir> && pnpm install
# then, in your AI editor:
#   Claude Code:       /substrat
#   Cursor / opencode: the new-vertical command

Don't add zod

Substrat is on Zod 4, and Zod schemas do not compose across copies or majors — mixing two makes z.object({ facility: entityRef }) fail at runtime with expected a Zod schema, pointing nowhere near the cause. Import z from contracts instead, and never install zod:

import { z, entityRef, money } from '@substrat-run/contracts';

Dependency-free by design

Node built-ins only, no build step. It can never break at install time and damage the name it exists to protect.

Note on the name

substrat on npm is an unrelated package — an HTML5 build system published in 2013. Substrat's own packages are all under the @substrat-run scope. Never npm install substrat.


Docs · Repo · Apache-2.0