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-custom-router

v1.0.0

Published

Custom route matching for express.js

Downloads

3

Readme

express-custom-router

Custom routing rules for express.js.

Installation

npm install --save express-custom-router

Usage

express-custom-router differs from the standard Express router, in that accepts a match function in place of a route path. The mounted controller will only be called if the match function returns true.

This allows much more flexibility in route handling.

const express = require('express');
const CustomRouter = require('express-custom-router');

const app = express();
const router = CustomRouter();

// Define routing rules for a controller
router.get(
    // Matching function receives the request,
    // and returns true/false
	req => (
	  req.url.startsWith('/foo') &&
	  req.method === 'GET' &&
	  req.headers['x-my-request-header'] = 'quux'
	),
	// Controller
	(req, res, next) => res.send('foo')
);

// Mount the router
app.use(router);

Why?

I am working on an application with very complicated route, which can accept all sorts of different options, in all sorts of different formats. Relying on Express' routing syntax makes handling these route very difficult.

With express-custom-router, I can parse the url however I want to, and then route based on this parsed route.

For example:

const app = express();
const router = CustomRouter();

// Middleware for manually parsing
// request parameters
router.use((req, res, next) => {
  req.opts = manuallyParseMyUrl(req.originalUrl);
  next();
});

// Setup routes, based on my manually parsed params
router.get(
  req => req.opts.foo === 'bar',
  (req, res) => res.send('foo is bar')
);
router.get(
  req => req.opts.foo === 'quux',
  (req, res) => res.send('foo is quux')
);

Reference

CustomRouter#all(match, controller)

Mount a controller for any HTTP verb

CustomRouter#get(match, controller)

Mount a controller for GET requests

CustomRouter#post(match, controller)

Mount a controller for POST requests

CustomRouter#put(match, controller)

Mount a controller for PUT requests

CustomRouter#delete(match, controller)

Mount a controller for DELETE requests

CustomRouter#use(middleware)

Mount middleware for all requests. Middleware must use the format (req, res, next) => {}