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

@exzi31/create-project-kit

v1.1.1

Published

A powerful CLI to scaffold production-ready full-stack projects with NestJS backend (PostgreSQL/MongoDB, Prisma/Mongoose, JWT auth, RBAC) and optional React/Next.js dashboard & frontend — all in seconds.

Downloads

628

Readme

@exzi31/create-project-kit

Scaffold production-ready full-stack projects in seconds.

create-project-kit is a batteries-included CLI that generates a complete, opinionated project structure — NestJS backend with authentication & RBAC, optional React/Next.js dashboard, and a public-facing frontend — all wired up and ready to run.

No boilerplate copy-pasting. No configuration guessing. Just answer a few prompts (or pass flags) and get a clean, working codebase.


✨ What you get

| Layer | Stack | |---|---| | Backend | NestJS · TypeScript / JavaScript · REST API | | Database | PostgreSQL (Prisma) · MongoDB (Prisma or Mongoose) | | Auth | JWT access + refresh tokens · Bcrypt hashing | | RBAC | Role-based access control out of the box | | Dashboard | Vite + React · Tailwind CSS · shadcn/ui (optional) | | Frontend | Vite React · React · Next.js · Tailwind / shadcn/ui (optional) | | Package managers | npm · pnpm · yarn | | Language | TypeScript or JavaScript everywhere |


🚀 Quick start

npx @exzi31/create-project-kit@latest

The interactive CLI will guide you through all choices. No flags required.


⚡ Non-interactive (CI / scripts)

Full example with every option spelled out:

npx @exzi31/create-project-kit@latest my-app \
  --backend-dir backend \
  --language ts \
  --database postgres \
  --dashboard \
  --dashboard-dir dashboard \
  --dashboard-ui tailwind-shadcn \
  --frontend \
  --frontend-dir frontend \
  --frontend-framework nextjs \
  --frontend-language ts \
  --frontend-ui tailwind-shadcn \
  --package-manager pnpm \
  --yes

MongoDB variants:

# MongoDB + Prisma
npx @exzi31/create-project-kit@latest my-app --database mongo --mongo-setup prisma

# MongoDB + Mongoose
npx @exzi31/create-project-kit@latest my-app --database mongo --mongo-setup mongoose --language ts

If you prefer to invoke the binary by name:

npx -p @exzi31/create-project-kit@latest create-project-kit

🛠️ All supported options

Backend

| Flag | Values | Default | |---|---|---| | --backend-dir <name> | any directory name | backend | | --language ts\|js | ts, js | prompted | | --database postgres\|mongo | postgres, mongo | prompted | | --mongo-setup prisma\|mongoose | prisma, mongoose | prompted |

Dashboard (optional admin UI)

| Flag | Values | |---|---| | --dashboard / --no-dashboard | include or skip | | --dashboard-dir <name> | directory name | | --dashboard-language ts\|js | TypeScript or JavaScript | | --dashboard-ui tailwind\|tailwind-shadcn | UI library preset |

Frontend (optional public-facing UI)

| Flag | Values | |---|---| | --frontend / --no-frontend | include or skip | | --frontend-dir <name> | directory name | | --frontend-framework vite-react\|react\|nextjs | framework choice | | --frontend-language ts\|js | TypeScript or JavaScript | | --frontend-ui tailwind\|tailwind-shadcn | UI library preset |

Misc

| Flag | Description | |---|---| | --package-manager npm\|pnpm\|yarn | package manager to use | | --skip-install | scaffold only, skip npm install | | --yes | accept all defaults, non-interactive |

Tip: --language ts|js is a shorthand that sets both --backend-language and --dashboard-language at once.


📁 Package layout

src/cli/
├── index.ts             # CLI entry: arg parsing, prompt orchestration
├── prompts.ts           # All @clack/prompts interactive questions
├── generator.ts         # File copy, overlay merging, post-processing
├── template-manifest.ts # Maps user choices → template files
├── overlays.ts          # Language / database overlay helpers
├── context.ts           # Shared context types
├── validations.ts       # Input validation rules
└── post-steps.ts        # Post-scaffold steps (install, git init, etc.)

templates/
├── backend/             # Base NestJS template + language/database overlays
├── dashboard/           # Optional dashboard templates + UI overlays
└── frontend/            # Frontend templates (Vite React, Next.js)

bin/
└── create-project-kit.js  # Published binary entrypoint

🧑‍💻 Local development

npm install
npm run build   # compile TypeScript → dist/
npm run dev     # run CLI from source via tsx

Verify everything works end-to-end:

npm run build
npm test        # runs smoke-matrix across all option combinations
npm pack        # inspect the tarball before publishing

📦 Publishing

To publish under your own scope:

  1. Update name in package.json, e.g. @my-org/create-project-kit.
  2. Build and verify:
npm install && npm run build && npm test && npm pack
  1. Log in and publish:
npm login
npm publish --access public

For CI publishing, use an npm automation token with publish permissions.


License

MIT © exzi31