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-react-frontend

v0.1.0

Published

CLI generator for production-ready React frontends with Vite or Next.js, plus opinionated defaults.

Readme

create-react-frontend

CLI generator for production-ready React frontends. One command, choose your stack:

  • React + Vite (SPA)
  • React + Next.js (App Router, SSR)

Both stacks come with sensible defaults already wired up:

  • TypeScript
  • Tailwind CSS (optional)
  • Prettier + prettier-plugin-tailwindcss
  • axios API client at src/lib/api.ts (optional)
  • cn() helper at src/lib/utils.ts (with Tailwind)
  • Husky + lint-staged (optional)
  • Folder structure: src/components, src/hooks, src/lib, src/types
  • .editorconfig, .nvmrc, .env.example

Usage

Quick mode (defaults: Tailwind, axios, Husky, git all enabled):

npm create react-frontend@latest
# or
pnpm create react-frontend

You'll only be asked for:

  1. Project name
  2. Stack (Vite or Next.js)

Custom mode (choose every option individually):

npm create react-frontend@latest custom
# or
pnpm create react-frontend custom

Asks for project name, stack, plus Tailwind, axios, Husky, git init.

How it works

The CLI delegates the base scaffold to the official tools (create-vite and create-next-app) and then layers shared + stack-specific overlays on top. This keeps the templates small and means you always get an up-to-date base.

Local development

cd generator
pnpm install
pnpm run create

Publishing

pnpm run build
npm publish