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-json-middleware

v0.1.0

Published

A simple minded way to pull in middleware based on a json config file.

Downloads

11

Readme

express-json-middleware

A simple minded way to pull in middleware based on a json config file.

This npm is very minimal. Currently its feature list is exactly what I need. If you need other types of routes supports, pull requests / issues are welcome.

Usage

Create a routes.json file (or just an in memory array), and pass it in along with the express, express app, and the path to your middlewares directory:

var express         = require('express'),
    app             = express(),
    createRoutes    = require('express-json-middleware'),
    routes          = require('./routes.json'),
    path            = require('path');
    

app.set('views'         , __dirname + '/views');
app.set('view engine'   , 'jade');

createRoutes({
    app         : app,
    express     : express,
    routes      : routes,
    middlewares : path.join(__dirname, 'middlewares')
});

app.listen(process.env.PORT);

Your routes array or routes.json should be an array of arrays. Each line has 3 items.

  1. The first item is the express use command or an express supported verb.
    1. use will, use the middleware on the app
    2. a verb will create a new isolated router and use the middlewares listed in the third item
  2. The second item is the routes that this should apply to, null if it should be set directly on the default router with no routes.
  3. The third item is the array of middlewares to be run. Each string will be required in with the middlewares base prefixed to it.

Additionally you can create named stacks of middleware using the "stack" word for the first item, a name for the second item, and a list of middlewares for the thired. These have to be included before being applied. You can include the named stack in your later lists of middlewares and it will be expanded to the full list. This is handy if you have long lists of repeated middlewares.

[
    [ "stack",  "addPageParts", ["addHeader", "addFotter"]],
    [ "GET",    "/",            ["addPageParts"]]
]

routes.json

[
  [ "use",      "/",                                ["static"]],
  [ "use",      "/api/v1",                          ["grasshopper"]],
  [ "GET",      "/admin*?",                         ["admin"]],
  [ "GET",      "/:category/:subcategory/:product", ["page/product", "notFound"]],
  [ "GET",      "/:category/:subcategory",          ["page/subcategory", "notFound"]],
  [ "GET",      "/:category",                       ["page/category", "notFound"]],
  [ "GET",      "*",                                ["notFound"]]
]