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

@pizzajsdev/route-collector

v0.9.0

Published

A framework-agnostic file-based route collector inspired by Next.js's App Router

Downloads

13

Readme

route-collector

A framework-agnostic file-based route collector inspired by Next.js's App Router

Features

Supports all route types of the official docs:

  • Root and index routes: Either index.tsx or page.tsx, but a segment folder is not required, e.g. posts.tsx is the same as posts/index.tsx
  • Dynamic Segments: posts/[id].tsx or posts/[id]/index.tsx
  • Optional Segments: [[lang]]/news.tsx
  • Splat/Wildcard routes: api/auth/[...].tsx
  • Layout routes: layout.tsx at any level, inheritable.
  • Extras inspired by Next:
    • Route grouping (via parentheses): (auth)/news.tsx will be /news. Has no effect more than code organisation purposes or for sharing the same layout without requiring a nested level.

Supports both .ts and .tsx files, depends if you use JSX inside or not.

Also supports .mdx and .md files for markdown pages, with an optional mdxRendererFile option to specify the route file to use as the renderer.

Installation

pnpm add @pizzajsdev/route-collector

Usage

Generic usage

You can use the collectRoutes function to collect the routes from the file system, and build your own route configuration with any framework that supports programmatically-generated routes.

import { collectRoutes } from '@pizzajsdev/route-collector/fs'

const routeDefinitions = collectRoutes({
  projectRoot: process.cwd() + '/src',
  routesDir: 'api',
  fileExtensions: ['.ts'],
  ignoredPaths: [],
  ignoredPathPrefix: '_',
})

for (const route of routeDefinitions) {
  // define routes e.g. with Hono, Elysia, etc.
}

Using with React Router

Edit the app/routes.ts file to use the generated routes.

// app/routes.ts
import { collectRoutes } from '@pizzajsdev/route-collector/react-router'

const routes = collectRoutes({
  projectRoot: process.cwd() + '/app',
  routesDir: 'routes',
  fileExtensions: ['.tsx', '.ts', '.mdx', '.md'],
  ignoredPaths: [],
  ignoredPathPrefix: '_',
})

export default routes