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-trio-app

v0.1.0

Published

CLI generator for production-oriented Next.js modular-monolith projects.

Readme

create-trio-app

Standalone generator for production-oriented Next.js modular-monolith projects.

Quick start

pnpm create trio-app my-app

This scaffolds ./my-app, then runs pnpm install, pnpm db:generate, and git init inside it. Skip any of those with the flags below.

Requirements

  • Node.js >= 24
  • pnpm 10+

Commands

Create a project

create-trio-app <target-dir> [options]

| Option | Description | | --- | --- | | --name <package-name> | npm package name (defaults to the target directory name) | | --skip-install | do not run pnpm install | | --skip-migrations | do not run pnpm db:generate | | --skip-git | do not run git init | | --force | overwrite conflicting files | | --dry-run | print the file list without writing |

Add a module

create-trio-app add module <module-name> [--project <path>] [--force] [--dry-run]

Scaffolds a new module under modules/<module-name>/ (domain, application, infrastructure, transport, plus index.ts) and registers it in sheriff.config.ts. --project defaults to the current directory.

Other

  • --help / -h — show usage
  • --version / -v — print package version

What's in the generated app

  • Next.js App Router with strict TypeScript
  • Drizzle ORM + Postgres
  • Kernel module and composition roots
  • Minimal admin and users modules
  • UI primitives
  • Vitest test setup
  • Sheriff architecture guardrails

Product modules (messaging, memberships, payments, AI workflows, etc.) are intentionally excluded from v1 — add them with add module or by hand.

Local development

pnpm install
pnpm build
node dist/cli.js ../my-app --skip-install --skip-git --skip-migrations
node dist/cli.js add module billing --project ../my-app

Useful scripts:

  • pnpm dev — run the CLI from sources via tsx
  • pnpm check — lint, typecheck, and test
  • pnpm test — Vitest only
  • pnpm test:coverage — Vitest with V8 coverage output
  • pnpm audit:prod — audit production dependencies
  • pnpm pack:dry-run — verify npm publish contents
  • pnpm format — Biome write mode

Release

Releases are manual. This project intentionally does not use Release Please or conventional-commit release automation.

pnpm version patch --no-git-tag-version
pnpm check
pnpm pack:dry-run

Commit the version bump, merge to main, then run the release workflow from GitHub Actions. The workflow verifies the package, checks that the version is not already published, and publishes to npm with provenance using NPM_TOKEN.