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

@numbered/create-bootstrap

v1.0.9

Published

Scaffold a new Numbered Studio project (Next.js + Sanity or Shopify Liquid) with full Sanity/GitHub/Vercel setup.

Readme

create-bootstrap

CLI to scaffold a new Numbered Studio project — Next.js + Sanity or Shopify Liquid, with Figma grid config baked in. Creates the project locally and wires it up end-to-end: Sanity project, GitHub repo, Vercel deployment, env vars, and preview domain.

Usage

npx @numbered/create-bootstrap
# or
bunx @numbered/create-bootstrap

Re-run it on an existing directory to resume setup — the CLI detects the project type and skips steps that are already done (Sanity project, GitHub repo, etc.).

What it does

Prompts:

  1. Project name — any string; internally slugified (e.g. My Projectmy-project)
  2. Template — Next.js + Sanity or Shopify Liquid (skipped if existing project)
  3. Shopify ecommerce support — for nextjs only; removes ~100 ecommerce files when disabled (default: no)
  4. Grid configuration — defaults to 24col desktop / 6col mobile
  5. Install dependencies — via bun
  6. Create Sanity project — creates remote project, injects all IDs/secrets into .env.local, prompts for SANITY_API_TOKEN
  7. Create GitHub repo — private repo under Numbered-com, initial commit on main, auto-push, then checkout staging branch
  8. Link Vercel project — under numbered-sandbox scope, sets apps/web as root, pushes env vars to all environments (parallel), adds {slug}.numbered.studio preview domain targeting staging

Each step is idempotent and skippable — re-running only runs what's missing.

Prerequisites

  • bun >=1.0
  • git + access to the Numbered-com GitHub org
  • gh (only for GitHub repo creation) — run gh auth login
  • Vercel CLI ≥ v51 (auto-installed globally if missing)
  • Sanity account — browser login on first run

Node.js >=22.

Templates

| Key | Label | Repo | | --------- | ---------------- | ------------------------- | | nextjs | Next.js + Sanity | Numbered-com/bootstrap | | shopify | Shopify Liquid | Numbered-com/jolie |

Next steps after scaffolding

cd my-project
bun run dev

If you skipped the Sanity step, copy .env.sample to .env.local and fill in the values manually.

Releasing

From staging:

bun run release          # patch (default)
bun run release:minor
bun run release:major

Each script bumps the version, commits, tags (v*), and pushes — the postversion hook auto-runs git push --follow-tags. The .github/workflows/publish.yml action picks up the tag and publishes to npm with provenance.

One-time setup: add an NPM_TOKEN repository secret (npm → Access Tokens → Automation token with publish rights to @numbered).