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

generate-next-route-constants

v0.0.2

Published

Generate route constants for Next.js App Directory

Readme

Next.js Route Constants Generator

A package that automatically scans Next.js App Directory routes and generates type-safe route constants.

Installation

npm install next-route-constants
# or
yarn add next-route-constants

Usage

1. CLI Options (Recommended)

# Basic usage
yarn generate-next-route

# With options
yarn generate-next-route --output ./src/constants --name routes.ts --input ./src/app

# Short options
yarn generate-next-route -o ./src/constants -n routes.ts -i ./src/app

CLI Options

  • -o, --output <path>: Output directory (default: ./src/constants)
  • -n, --name <filename>: Output filename (default: routes.ts)
  • -i, --input <path>: App directory path (default: ./src/app)
  • -c, --config <path>: Configuration file path (optional)

2. Configuration File (Optional)

Create a route-constants.config.js file in your project root:

module.exports = {
  outputDir: './src/constants',  // Output directory
  filename: 'routes.ts',         // Filename
  inputDir: './src/app'          // App directory path
};

Note: CLI options take precedence over configuration files.

3. Using Generated Constants

import { ROUTES } from './constants/routes';

// Usage examples
console.log(ROUTES.Home); // '/'
console.log(ROUTES.User.Login); // '/user/login'

Usage Examples

# Basic usage
yarn generate-next-route

# Custom output path
yarn generate-next-route -o ./lib/constants -n app-routes.ts

# Different app directory
yarn generate-next-route -i ./app -o ./constants

# All options
yarn generate-next-route \
  --input ./src/app \
  --output ./src/lib/constants \
  --name navigation.ts

Features

⚠️ Important: route.json Required

Only pages with route.json files will be generated as route constants.

route.json Configuration

Create a route.json file in each page directory to configure routes:

{
  "name": "Dashboard",           // Required: Route name
  "groupName": "Admin"          // Optional: Group name for grouping
}

🔄 Inheritance Feature

Child directories automatically inherit groupName from parent directories.

posts/route.json → { "name": "Posts", "groupName": "Posts" }
├── [id]/route.json → { "name": "Detail" }  // Inherits "Posts"
│   └── edit/route.json → { "name": "Edit" }  // Inherits "Posts"

Inheritance Priority:

  1. Own groupName (highest priority)
  2. Nearest parent's groupName
  3. No grouping

1. Basic Routing

src/app/
├── page.tsx
├── route.json                 → { "name": "Home" } → { "Home": "/" }
├── about/
│   ├── page.tsx
│   └── route.json            → { "name": "About" } → { "About": "/about" }

2. Grouping via Inheritance

src/app/
├── posts/
│   ├── page.tsx
│   ├── route.json            → { "name": "Posts", "groupName": "Posts" }
│   ├── [id]/
│   │   ├── page.tsx
│   │   ├── route.json        → { "name": "Detail" } // Inherits "Posts"
│   │   └── edit/
│   │       ├── page.tsx
│   │       └── route.json    → { "name": "Edit" } // Inherits "Posts"

Result:
{
  "Posts": {
    "Posts": "/posts",
    "Detail": "/posts/[id]",
    "Edit": "/posts/[id]/edit"
  }
}

3. Inheritance Override

src/app/
├── posts/
│   ├── route.json            → { "name": "Posts", "groupName": "Posts" }
│   └── [id]/
│       ├── route.json        → { "name": "Detail" } // Inherits "Posts"
│       └── comments/
│           └── route.json    → { "name": "Comments", "groupName": "Comments" } // Override

Result:
{
  "Posts": {
    "Posts": "/posts",
    "Detail": "/posts/[id]"
  },
  "Comments": {
    "Comments": "/posts/[id]/comments"
  }
}

4. Dynamic Routing

src/app/
├── posts/
│   └── [id]/
│       ├── page.tsx
│       └── route.json        → { "name": "Detail", "groupName": "Posts" }

Result:
{
  "Posts": {
    "Detail": "/posts/[id]"
  }
}

5. Route Groups

src/app/
├── (auth)/
│   ├── login/
│   │   ├── page.tsx
│   │   └── route.json        → { "name": "Login" } → { "Login": "/login" }
│   └── signup/
│       ├── page.tsx
│       └── route.json        → { "name": "Signup" } → { "Signup": "/signup" }

Generated File Example

// This file is auto-generated. Do not edit manually.
// Generated on 2024-01-01T00:00:00.000Z
// Routes are configured via route.json files in each page directory

export const ROUTES = {
  "Home": "/",
  "About": "/about",
  "User": {
    "Login": "/user/login",
    "Profile": "/user/profile"
  },
  "Posts": {
    "Posts": "/posts",
    "Detail": "/posts/[id]",
    "Edit": "/posts/[id]/edit"
  }
} as const;

export type RouteKeys = keyof typeof ROUTES;

Monorepo Support

The package automatically detects monorepo structures:

  • Current project's src/app
  • Current project's app
  • Parent directories' src/app (up to 2 levels)

Configuration Priority

  1. CLI options (highest priority)
  2. CLI --config specified configuration file
  3. route-constants.config.js
  4. route-constants.config.ts
  5. Configuration extracted from next.config.js
  6. Default values (lowest priority)

Development

# Install dependencies
npm install

# Build
npm run build

# Local testing
npm link
cd /path/to/test/project
npm link next-route-constants
yarn generate-next-route

License

MIT