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

route-imperator

v1.0.1

Published

Divide et impera. Organize declarative routes in an imperative way for trie, radix or prefix routers

Downloads

21

Readme

Divide et impera

route-imperator helps you organizing declarative routes in an imperative way. After collecting all your routes, you may use any router of your choice.

This program assumes that all routes are orthogonal, therefore is a good match for trie, radix or prefix routers. It allows to nest collections of routes and to apply middlewares.

Routers with support for route-imperator:

Installation

npm install --save route-imperator

Example

// routes/users.js

const routes = require('route-imperator')()

routes
.get('/', searchUsers)
.get('/:id', findUser)

// this middlware only applies to subsequent route definitions
routes.use(verifyLoggedIn)

routes
.patch('/', modifyUser)
.delete('/', deleteUser, notifyDeletion)

module.exports = routes


// routes/index.js

const routes = require('route-imperator')()

const users = require('./users');
const messages = require('./messages');

// Nest routes using a path prefix
routes.load('/users', users)
routes.load('/messages', messages)

module.exports = routes


// router.js

const router = require('koa-my-way')()
const routes = require('./routes')

router.load(routes);

module.exports = router;

API

routes.use(...middlewares)

After a middleware is defined, all subsequent routes will use that middleware. Middlewares are applied in the order that they are defined.


// No middlewares applied
routes.get('/', searchPhotos);

routes.use(mid1);

// mid1 executed before findPhoto
routes.get('/:id', findPhoto)

routes.use(mid2, mid3);
routes.use(mid4);

// This route has mid1, mid2, mid3 and mid4 and createPhoto
routes.post('/', createPhoto)

routes.on(method, path, ...handlers)

Defines a route, there are also shorthand methods available


routes.on('GET', '/', searchPhotos);
routes.on('GET', '/:id', findPhoto);
routes.on('POST', '/d', verifyLoggedIn, uploadPhoto);

// Equivalent calls using shorthand methods
routes
.get('/', searchPhotos)
.get('/:id', findPhoto)
.post('/', verifyLoggedIn, uploadPhoto)

routes.load([path,] instance)


// router/users.js

routes.use(usersMiddleware)

routes
.get('/', searchUsers)
.get('/:id', findUser)
.post('/', robotFilter, createUser)

module.exports = routes


// router/index.js

const users = require('./users');

routes.use(generalMiddleware)

routes.load('/users', users)

// Here the routes look like this
//  [{
//    method: 'GET', 
//    path: '/users/', 
//    handlers: [
//      generalMiddlware, 
//      usersMiddlware, 
//      searchUsers, 
//    ]
//  },{
//    method: 'GET', 
//    path: '/users/:id', 
//    handlers: [
//      generalMiddlware, 
//      usersMiddlware, 
//      findUser, 
//    ]
//  },
//  },{
//    method: 'POST', 
//    path: '/users/', 
//    handlers: [
//      generalMiddlware, 
//      usersMiddlware, 
//      robotFilter,
//      createUser, 
//    ]
//  }]

Non nestable features

The following features cannot be (easily) applied to nested tries. The can only be implemented in the root of the trie router. Consult your router manual for more information, or construct yourself a general middleware.

  • Default route
  • Handle 405 errors
  • Handle 501 errors