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

thruway

v0.2.1

Published

A tiny middleware stack with error handler support and no dependencies

Downloads

15

Readme

thruway

A tiny middleware stack with error handler support and no dependencies

NPM version Build Status

Installation

$ npm install thruway

Usage

thruway creates a generic middleware stack that follows the express middleware stack semantics closely. It keeps the concept of passing two arguments for the "request" and "response", except that the "request" may be any value you wish and the "response" is a function that will exit the middleware stack.

var stack = require('thruway')();
var assert = require('assert');

// This is a middleware function that will receive
// the `req` value and `res` and `next` continuations.
// Calling `res(err, val)` will skip to the final callback
// while calling `next(err)` will continue down the stack.
stack.use(function(req, res, next){
	assert.equal(req, 'REQ');
	next();
});

// This middleware calls `res` with the `val` value to
// pass to the final callback.
stack.use(function(req, res, next){
	res(null, 'VAL');
});

// This is an error handler (note the arity of 4 and the
// first parameter, `err`). It will only be called if
// a middleware passes an error to `next`.
stack.use(function(err, req, res, next){
	throw err; // You should handle the error here instead
});

// This kicks off the middleware stack and calls the
// callback at the end.
stack('REQ', function(err, val){
	assert.equal(err, null);
	assert.equal(val, 'VAL');
});

Middleware

Middleware are functions with the signature fn(req, res, next), where:

  • req is the value you passed to the stack. This can be anything you like and is only called "req" to mimic the express API.
  • res(err, val) exits the stack and calls the final callback. No other middleware or error handlers will be run.
  • next(err) yields control to the next middleware. If an error is yielded, the error handler stack will be run. If an error is not yielded and there are no more middleware, the final callback will be invoked with val = undefined.

Error Handlers

Error handlers are functions with the signature fn(err, req, res, next), where:

  • err is the error that was passed to the stack. Each error handler is expected to pass this or another error to either res or next.
  • req is the value you passed to the stack. This can be anything you like and is only called "req" to mimic the express API.
  • res(err, val) exits the stack and calls the final callback. Error handlers must pass an error to this function. No other middleware or error handlers will be run.
  • next(err) yields control to the next error handler. Error handlers must pass an error to this function. If there are no more error handlers, the final callback will be invoked with val = undefined.

License

ISC License