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 🙏

© 2024 – Pkg Stats / Ryan Hefner

express-ls-routes

v1.0.2

Published

Cli and middleware to list routes in your express app

Downloads

106

Readme

express-ls-routes

Updated: supports express3 and express4!

It's a cli that lets you list the routes in your express app:

$ routes

GET    /my-app/:id
POST   /my-app
...

And a middleware that can expose the same information in a route in your app:

$ curl localhost:3000

[
  "GET   /my-app/:id",
  "POST  /my-app"
  ...
]

Install

npm install express-ls-routes --save

CLI

Running

Simply run:

routes

Note that this requires ./node_modules/.bin to be in your path. If it's not, use the command:

node_modules/.bin/routes

In this case, definitely consider adding an npm scripts entry (see below).

Setup

The cli depends on your routes being listed in one file. It depends on your file being formatted like this, where your express app is called 'app' or 'server'. The route handlers can be inline functions or references to other modules.

app.get('/my-app/:id', ...)
app.post('/my-app', ...)
...

This is because the cli doesn't actually run the express app. It just parses the static js file contents to derive your app's routes.

routes.js Location

The cli shouldn't require configuration if you use the default file locations. By default, the cli expects the routes.js file to be located at:

app/config/routes.js

You can change this behavior by doing two things:

  • Run the cli via npm scripts by adding it in package.json:
"scripts": {
  "routes": "routes"
}
  • Add config in package.json for the routes.js location:
"config": {
  "routes": "app/another/location/myRoutes.js"
}

Middleware

Setup

The middleware doesn't depend on your routes.js file being in any specific location as in the case of the cli because it actually interrogates your express app to determine what routes have been attached to it. But, because of this, you must use this middleware after all the routes you want the middleware to know about have been attached. This will mean that you usually put the endpoint that lists routes as the last route in your app.

Pass your express app to the middleware, and it will attach routes as json routes on the request (req) object:

var lsRoutes = require('express-ls-routes')

app.get('/', lsRoutes(app), function (req, res) {
  res.json(200, req.routes)
})