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

@keleran/routing

v4.0.0

Published

Routing utilities for Node.js projects

Downloads

40

Readme

@keleran/routing

Utilities to simplify request routing in Node.js projects.
Use ESM, require Node.js 16+.

GitHub Workflow Status

Installation

$ npm i @keleran/routing
import {discover, mount} from '@keleran/routing';

discover

Returns a flat list of route handlers found in the specified directory. If you don't need to work with the list before mounting, use mount directly - it returns the same data.

// [{route: String, method: String, source: Object, pipeline: Array}, ...]
const handlers = await discover({dir: 'routes'});

mount

Reads a file tree and mounts request handlers to the specified Express app.

Request handler is a file named as "HTTP_METHOD.js" (get.js, post.js, etc.) that exports an object with the following properties:

  1. "rateLimit" (optional) - a string or an object that defines rate limiting options for the rate-limiter-flexible library.
    The string is parsed with the ms library, "1s" means "allow 1 request per second from this IP".
    The object is passed to rate-limiter-flexible as is. HTTP 429 will be thrown upon exceeding the limit.
  2. "authorize" (optional) - an authorization function that MUST return true for request to be processed. Otherwise it throws HTTP 403 using the http-errors library. Supplied with the "req" and "res" arguments. Can be async.
  3. "middleware" (optional) - a function or an array of functions that are regular middleware with the "req", "res", and "next" arguments supplied.
  4. "handle" - the main function that handles the request. Supplied with the "req" and "res" arguments. Can be async.

The order of execution matches the order listed above.

Example

The following tree:

routes
├── =
│   └── get.js
└── route
    ├── get.js
    └── =param-name
        └── get.js

With the call:

await mount({dir: 'routes', app, route: '/test'});

Will be mounted like this (notice the order and param/wildcard substitution):

app.get('/test/route', /* handler defined in routes/route/get.js */);
app.get('/test/route/:paramName', /* handler defined in routes/route/=param-name/get.js */);
app.get('/test/*', /* handler defined in routes/=/get.js */);