01 / Technologies / Framework

Detect Next.js in any GitHub repo

Next.js is Vercel's React framework for full-stack web apps: file-based routing, server components, static generation and API routes in one package.

Why show Next.js on your README

Contributors immediately know whether to expect the App Router, server actions or a classic Pages setup, so it's one of the first things worth surfacing.

How Next.js is detected

Stack Fingerprint reads the repo's full file tree in one GitHub API call and flags Next.js when it finds any of these:

  • Files or folders: /^next\.config\.(js|ts|mjs|cjs)$/
  • Dependencies in package.json: next

Next.js README badge

A static badge you can paste anywhere in Markdown:

Next.js badge

Markdown
![Next.js](https://img.shields.io/badge/Next.js-000000?style=for-the-badge&logo=nextdotjs&logoColor=white)

Or let the repo describe itself

Static badges go stale the moment you swap a dependency. A Stack Fingerprint card is generated from the repo, so Next.js (and everything around it) appears or disappears on its own:

Tech stack card for vercel/commerce
vercel/commerce · generated live from the repo
README.md
[![Stack Fingerprint](https://stackfingerprint.vercel.app/api/card?repo=OWNER/REPO)](https://stackfingerprint.vercel.app/?repo=OWNER/REPO)

Replace OWNER/REPO with your repository, or open the builder to pick a theme and layout.

02 / Related articles