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

webgenix-code

v0.1.2

Published

Scaffold a slim TN³PR full-stack TypeScript monorepo (Next.js + Nest + Prisma + Redis).

Readme

webgenix-code

Scaffold a slim, production-ready TN³PR full-stack TypeScript monorepo in seconds: Next.js + NestJS + Prisma + PostgreSQL + Redis.

webgenix-code is a scaffolding CLI that generates a typed end-to-end monorepo — complete with auth, caching, shared types, and a polished shadcn/ui frontend — then prunes whatever you don't want. No boilerplate to delete, no wiring to untangle.

Quick start

pnpm dlx webgenix-code my-app
# or:  npx webgenix-code my-app
# or:  bunx webgenix-code my-app

Interactive prompts collect a project name, namespace, and optional features. Then:

cd my-app
docker compose -f docker-compose.dev.yml up -d   # PostgreSQL + Redis
pnpm db:sync
pnpm db:seed
pnpm dev        # web on :3000, api on :3001

Non-interactive usage

All flags are optional. Pass -y to accept every default and skip prompts.

pnpm dlx webgenix-code my-app --namespace acme --no-auth --no-redis -y

Flags

| Flag | Effect | | --- | --- | | --namespace <ns> | Scope packages as @<ns>/* (default: project name slug) | | --no-auth | Drop the auth package + web auth wiring | | --no-redis | Drop the redis package (also disables auth + examples) | | --no-examples | Drop example feature code (also disables auth) | | --no-testing | Strip test harnesses (standalone) | | --no-git | Skip git init | | --pm <pnpm\|npm\|yarn\|bun> | Pin a package manager | | -y | Use all defaults, no prompts | | --ai | Optional: generate extra modules via a local Ollama model (skips cleanly if Ollama is unavailable) |

Feature dependency cascade

examples → auth → redis. Disabling a feature disables everything downstream — auth uses redis for sessions, and examples are auth-guarded. The CLI prints a warning whenever it coerces your selection. Only --no-testing is standalone.

What you get

A pnpm + Turbo monorepo:

apps/
  web/        # Next.js 16 (App Router, Turbopack, React 19, shadcn/ui)
  api/        # NestJS + Express
packages/
  ui/               # shadcn/ui + Tailwind v4 design tokens
  database/         # Prisma schema + client (PostgreSQL)
  shared/           # Zod schemas + types, shared across web & api
  auth/             # JWT auth (opt-in)
  redis/            # Cache helpers (opt-in)
  tsconfig/ eslint-config/ prettier-config/
docker-compose.dev.yml, docker-compose.prod.yml

Core packages (ui, database, shared, the config packages) are always included. auth and redis are opt-in; example code and the testing harness are opt-in feature sets. Type-safe communication flows across the whole stack.

Why a CLI and not a template clone?

Every scaffolded project starts clean: @webgenix placeholders are swapped to @<namespace>, disabled features are deleted (not commented out), and the import graph is reconciled so there are no dangling references. The result installs and runs on first try.

Requirements

  • Node.js ≥ 20
  • pnpm 10.20.0
  • Docker (for PostgreSQL and Redis)

Development

pnpm install
pnpm build          # tsup -> dist/index.js
pnpm test           # vitest (unit + scaffold-matrix integration)
pnpm type-check     # tsc --noEmit

Run locally against a temp dir:

node packages/cli/dist/index.js ../my-test -y

License

MIT