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

express-config-routes

v1.0.1

Published

A simple extention for config Express router

Readme

express-config-routes

express-config-routes is library for dynamic nested routes in express

Installation

npm install express-config-routes

or with yarn

yarn add express-config-routes

Usage

Example:

import configRoutes from 'express-config-routes'
import express from 'express'

const app = express()

const options = {
  routeDir: '/routes', // DEFAULT '/routes' NOT REQUIRED
  absolutePath: 'YOUR ABSOLUTE PATH', // NOT REQUIRED
}

app.use(configRoutes(options))

When you use both of routeDir and absolutePath, absolutePath overrides routeDir

This file tree:

routes/
--| users/
-----| post.js
-----| middleware.js
-----| _id/
-------| get.js
--| books/
-----| _bookId/
--------| authors/
-----------| _authorId/
-------------| get.js
--| get.js

generate express Route path:

/users/
/users/:id
/books/:bookId/authors/:authorId
/

each js file's form

export default (req, res) => {
  res.send('ok')
}

or

export default (req, res) => {
  res.send('ok')
}

Use middlewares:

Using under method

// get.js
export default (req, res) => {
  console.log(req.params.id)
  res.send('req.params.id is ' + req.params.id)
}

const middle = (req, res, next) => {
  console.log(req.method)
  next()
}

const middle2 = (req, res, next) => {
  console.log('bar')
  next()
}

export const middleware = [middle, middle2]

Using under any file

// middleware.js
const middleware01 = (req, res, next) {
  cosole.log('middleware01')
  next()
}
const middleware02 = (req, res, next) {
  cosole.log('middleware02')
  next()
}
export default [middleware01, middleware02]

If use middleware overall, should set it the execution file