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-cutting-edge-nextjs-app

v1.4.0

Published

Scaffold a Cutting Edge Nextjs app

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

jadetamjadetam

Keywords

Readme

create-cutting-edge-nextjs-app

Scaffold a production-ready Next.js template with strong defaults aligned to official docs and current best practices.
Built for teams who want to ship faster with less setup debate, cleaner architecture, and reliable foundations from day one.

Quick start

pnpm create cutting-edge-nextjs-app@latest
# or
npx create-cutting-edge-nextjs-app@latest
# or
yarn create cutting-edge-nextjs-app
# or
bunx create-cutting-edge-nextjs-app@latest

Requires Node.js 20+

Why this template?

  • Strong defaults, fewer decisions
    Start with a curated stack and conventions that reduce setup churn.

  • Aligned with official docs
    Configuration and patterns follow current framework/library guidance, not outdated boilerplate.

  • Built for real product workflows
    Includes public/marketing pages, auth flows, and a CSR dashboard architecture.

  • AI contributor ready
    Ships with explicit project structure and contributor rules in the generated template for consistent AI-assisted changes.

Tech stack

Core app stack

| Category | Library | |---|---| | Framework | Next.js 16 (App Router) | | UI | React 19 | | Language | TypeScript | | Styling | Tailwind CSS 4 + DaisyUI | | i18n | next-intl | | Server state | @tanstack/react-query | | Forms | @tanstack/react-form + @tanstack/zod-form-adapter | | Validation | Zod | | Animation | GSAP | | Notifications | Sonner | | Backend default | Firebase |

Quality and developer tooling

| Category | Library | |---|---| | Component development | Storybook 10 (@storybook/nextjs) | | Unit/Integration testing | Vitest + Testing Library | | E2E testing | Playwright | | Linting | ESLint 9 + eslint-config-next | | Type checking | TypeScript (tsc --noEmit) | | Local backend workflow | Firebase Emulator Suite |

UI asset/tooling integrations

| Category | Library | |---|---| | Icon system | Iconify (@iconify/tailwind4, Fluent + Simple Icons) | | Analytics | @vercel/analytics |

Backend architecture

The generated app uses an adapter-oriented backend design with Firebase configured as the production-ready default.
It is structured to be extensible, so teams can add REST API adapters later without rewriting feature-level UI flows.