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

platform-app-cli

v0.1.0

Published

Scaffold enterprise-grade React/Next.js apps with platform patterns in under a minute

Readme

platform-app-cli

Scaffold production-ready React/Next.js/Node.js apps with enterprise patterns in under a minute.

npx platform-app-cli my-app

Templates

| Template | What's included | |----------|----------------| | React + Vite | React 19, TypeScript strict, ESLint, Vite 6 | | Next.js 15 (App Router) | Auth.js v5 (GitHub OAuth, JWT), OpenFeature flags, GitHub Actions CI | | Node.js API (Fastify) | Fastify 5, OpenAPI/Swagger UI, CORS, Helmet, GitHub Actions CI |

Why

create-t3-app gives you type-safety. This gives you platform patterns — the architectural decisions a platform engineering team makes for a production app:

  • Auth wired from day one (no weekend spent reading Auth.js docs)
  • Feature flags via OpenFeature — provider-agnostic, swap your backend later
  • OpenAPI spec auto-generated from route schemas — no manual documentation
  • CI/CD included — push and your first build runs

Usage

# Run directly (no install needed)
npx platform-app-cli my-app

# Or pass the project name as an argument to skip the first prompt
npx platform-app-cli my-app

The CLI will ask:

  1. Template — React + Vite / Next.js 15 / Node.js API
  2. Features — template-specific extras (Vercel config, Dockerfile)
  3. Git init — initialise a git repository
  4. Install deps — run npm install automatically

Templates in depth

React + Vite

src/
├── main.tsx
└── App.tsx

Minimal and clean. TypeScript strict mode, ESLint configured. Start here if you're building a SPA.

Next.js 15 (App Router)

src/
├── app/
│   ├── page.tsx              — force-dynamic (safe with auth())
│   ├── layout.tsx
│   ├── auth/sign-in|out/     — Server Action forms
│   └── api/auth/[...nextauth] — Auth.js handler
├── auth.ts                   — NextAuth v5-beta: GitHub OAuth, JWT
├── components/
│   ├── providers.tsx         — OpenFeatureProvider
│   └── home-content.tsx      — useBooleanFlagValue hook usage
└── lib/flags.ts              — typed flag definitions, InMemoryProvider

Auth setup — after scaffolding:

cp .env.example .env.local
# Add your AUTH_SECRET (npx auth secret) and GitHub OAuth credentials

Feature flags — defined in src/lib/flags.ts. Swap InMemoryProvider with LaunchDarkly, Flagsmith, or any OpenFeature-compliant provider.

Node.js API (Fastify)

src/
├── index.ts          — PORT from env, host 0.0.0.0 (container-safe)
├── server.ts         — plugin registration order: security → swagger → routes → swagger-ui
├── plugins/
│   ├── swagger.ts    — @fastify/swagger (before routes) + swagger-ui (after)
│   └── security.ts   — @fastify/cors + @fastify/helmet
└── routes/
    ├── health.ts     — GET /health → {status, uptime, timestamp}
    └── items.ts      — CRUD /api/v1/items with full OpenAPI schema

Swagger UI available at http://localhost:3000/documentation after npm run dev.

Development

git clone https://github.com/RahulTinku/platform-app-cli
cd platform-app-cli
npm install
npm run build
node dist/index.js my-test-app

Roadmap

  • [x] Prettier + lint-staged + Husky pre-commit hooks (selectable feature, all 3 templates)
  • [x] Next.js template: Prisma + database adapter for Auth.js (selectable feature)
  • [x] Node.js template: Docker multi-stage build (selectable feature)
  • [x] --template flag to skip interactive prompts (for CI/scripts)
  • [x] Publish to npm — package ready, publish off VPN when ready

License

MIT