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

next-flat-routes

v0.1.6

Published

A CLI tool to simplify Next.js routing by allowing developers to work with a flat route structure

Readme

next-flat-routes

npm version Github Actions

Enabling flat routes for Next.js

Table of Contents


Introduction

With the introduction of Next.js 13, a new folder-based routing mechanism was unveiled. While this approach offers powerful and flexible routing capabilities, it brings with it the challenge of managing deeply nested route files. In large projects with a myriad of routes, locating a specific route or deciphering the intricate structure of the application becomes increasingly complex.

Enter next-flat-routes.

Designed specifically for Next.js 13, next-flat-routes is a CLI tool that allows developers to work with a flat route file structure that is easier to manage and understand. With next-flat-routes your routes can be structured like this:

app/
|-- shop/
    |-- routes/
        |-- basket.(page).tsx
        |-- product.(page).tsx
        |-- product.[id].(page).tsx

... and next-flat-routes will ensure that these routes are transformed into the nested format that Next.js expects.

app/
|-- shop/
    |-- (.routes)/
    |   |-- basket/
    |   |   |-- page.tsx
    |   |-- product/
    |       |-- page.tsx
    |       |-- [id]/
    |           |-- page.tsx
    |-- routes/
        |-- basket.(page).tsx
        |-- product.(page).tsx
        |-- product.[id].(page).tsx

Usage

To start using the next-flat-routes, run the following command in the Next.js project root:

npx @ifyio/next-flat-routes@latest

This will initiate the next-flat-routes CLI in watch mode.

Then add flat route files within any /routes/ folder located within the app directory. As you add, rename, or remove these flat route files, the equivalent nested route file will be generated or updated within a parallel /(.routes)/ directory.

Note: The /(.routes)/ directory should be considered as "private", similar to the .next directory that Next.js uses for its build output. Files within this directory are auto-generated and should not be manually edited.

About flat routes

Flat routes can be created for page.tsx, layout.tsx, loading.tsx, error.tsx and route.tsx files. All that is required is for their flat route equivalent filenames to end with .(page).tsx, .(layout).tsx, .(loading).tsx, .(error).tsx and .(route).tsx .

Example:

/app/shop/routes/basket.(page).tsx
/app/shop/routes/product.(layout).tsx
/app/shop/routes/product.[productId].(page).tsx
/app/admin/routes/settings.(page).tsx

Additionally, each route segment should be delimited by a period (.), as seen in the example above.

Index route files

For flat index route files, there's no need to prefix the route filename. For instance, the admin homepage will be:

/app/admin/(page).tsx
/app/admin/(error).tsx
/app/admin/(layout).tsx
/app/admin/(loading).tsx

Supported file extensions

next-flat-routes supports .ts, .tsx, .jsx, and .js file extensions for flat route files.

License

MIT