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

react-router-module

v0.1.1

Published

A module system for React Router that allows you to load route modules from node_modules or any other location.

Downloads

246

Readme

react-router-module

Load React Router route modules from installed packages or other resolvable module paths.

This package helps you build a plugin-style architecture for React Router apps. Each external module exports a route config as its default export, and can optionally export a menu definition that your host app can render in navigation.

Installation

npm install react-router-module

Peer dependencies:

  • @react-router/dev@^7
  • typescript@^5

What it does

moduleLoader() accepts a list of module specifiers and returns two async helpers:

  • getRoutes() resolves each module and returns React Router route entries
  • getMenus() returns any exported menu metadata

When a module exports a route file like ./page.tsx, this package rewrites that file path to an absolute path based on the installed module location, so React Router can load it correctly.

Host app usage

import { moduleLoader } from "react-router-module";

const modules = moduleLoader(["teams"]);

export default [
	index("routes/home.tsx"),
	route("/dashboard", "routes/dashboard.tsx"),
	...(await modules.getRoutes()),
] satisfies RouteConfig;

You can also load menus for your sidebar or app navigation:

const menus = await modules.getMenus();

Module authoring

An external module should export:

  • a default React Router route config entry
  • an optional menu object or menu() function

Example:

import { route } from "@react-router/dev/routes";

export const menu = {
	name: "Teams",
	icon: "users",
	to: "/teams/1",
};

export default route("/teams/:teamId", "./page.tsx");

Menu type

type ModuleMenu = {
	name: string;
	icon?: React.ReactNode | string;
	to: `/${string}`;
};

menu can be either:

  • a plain object matching ModuleMenu
  • a function returning ModuleMenu

This is useful when menu values need to be computed at load time.

API

moduleLoader(modules: string[])

Creates a lazy loader for one or more route modules.

Parameters:

  • modules: package names or other Node-resolvable module specifiers

Returns:

{
	getRoutes: () => Promise<RouteConfigEntry[]>;
	getMenus: () => Promise<ModuleMenu[]>;
}

Notes

  • Modules are resolved with Node's require.resolve
  • Route file values must be strings
  • Child routes are supported and their file paths are also resolved recursively
  • The module list is loaded once and shared between getRoutes() and getMenus()

Development

npm run typecheck
npm run build