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

v0.1.0

Published

wrap express request/response with node domains

Downloads

18,259

Readme

express-domain-middleware

Build Status

Hi! Are you using process.uncaughtException in your express apps to keep them running?

OR...Do you just let your process crash on any unhandled exception and restart it?

Do you find it hard to pass "request.id" to 8 nested database calls so you can keep a context of what request you're working on?

How do you associate log entries with a specific request? Passing the request around everywhere again?

Domains can help.

USE DOMAINS

First, read this

Second, realize once you enable domains process.domain will give you the active domain.

Third, use this middleware to bind each request/response pair to its own domain.

express.use(require('domain-middleware'));

domain-middleware api

var domainMiddlewaire = require('express-domain-middleware');

domainMiddleware = function(req, res, next)

Exports a function matching the signature of express middleware. Binds incomming request & response from express to a new domain. Assigns the domain a unique id by calling domainMiddleware.id(req).

If the domain emits an error event, domainMiddleware will call next(err) with the error event from the domain. This allows existing express specific error handling middleware to function as if the error was hanlded by your application code. Allow me to demonstrate with an example:

///old-school
app.get('/error', function(req, res, next) {
  db.query('SELECT happiness()', function(err, rows) {
    if(err) return next(err);    
    fs.readFile('alskdjflasd', function(err, contents) {
      if(err) return next(err);
      process.nextTick(function() {
        throw new Error("congratulations, your node process crashed and the user request disconnected in a jarring way");
      });
    });
  })
});

now with less crashing...

//with domain-middleware
app.use(require('domain-middleware'));
app.use(app.router);
app.use(function errorHandler(err, req, res, next) {
  console.log('error on request %d %s %s: %j', process.domain.id, req.method, req.url, err);
  res.send(500, "Something bad happened. :(");
  if(err.domain) {
    //you should think about gracefully stopping & respawning your server
    //since an unhandled error might put your application into an unknown state
  }
});
app.get('/error', function(req, res, next) {
  db.query('SELECT happiness()', process.domain.intercept(function(rows) {
    fs.readFile('asldkfjasdf', process.domain.intercept(function(contents) {
      process.nextTick(process.domain.inercept(function() {
        throw new Error("The individual request will be passed to the express error handler, and your application will keep running.");
      }));
    }));
  }));
});

I have to recommend using okay to gracefully fallback in the absence of domains. Plus..it's terse. Go, code golf!

var ok = require('okay');
app.use(require('domain-middleware'));
app.use(app.router);
app.use(function errorHandler(err, req, res, next) {
  console.log('error on request %d %s %s: %j', process.domain.id, req.method, req.url, err);
  res.send(500, "Something bad happened. :(");
});
app.get('/error', function(req, res, next) {
  db.query('SELECT happiness()', ok(next, function(rows) {
    fs.readFile('asldkfjasdf', ok(next, function(contents) {
      process.nextTick(ok(next, function() {
        throw new Error("The individual request will be passed to the express error handler, and your application will keep running.");
      }));
    }));
  }));
});

license

MIT