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

dominion

v0.2.2

Published

A domain middleware for express apps, capable of handling multiple apps.

Downloads

4

Readme

dominion

Coverage Status Build Status

npm npm

Domain middleware for Express and vanilla Node.js. Dominion has no production dependencies.

Dominion will attempt to gracefully close all servers registered with it when any requests using the domain middleware throw an otherwise uncaught exception. Dominion is intended to be used with on cluster workers, but will also work on master instances to make testing a little easier for its dependents.

Usage

Dominion provides both a middleware function and a function to add server instances. Dominion is slightly atypical in that it requires references to all server instances that a worker is running. This middleware must only be used on cluster worker processes. Cluster and domain are two sides of the same coin, so this should be no surprise.

var dominion = require('dominion');
var express = require('express');

var app = express();

// Add at the beginning of the middleware chain.
app.use(dominion.middleware);

// Add other middleware and routes...

// The server object is returned from `app.listen`.
var server = app.listen(3000, function () {
    console.log('Server listening.');
});

// Register the server object with dominion. This is required!
dominion.addServer(server);

// Give dominion a chance to finish its job, but avoid hangs.
dominion.once('shutdown', function () {
    var killtimer = setTimeout(function () {
        process.exit(1);
    }, 5000);

    killtimer.unref();
});

To use with vanilla Node HTTP servers, you can spoof the vanilla method:

var http = require('http');
var dominion = require('dominion');

// Give dominion a chance to finish its job, but avoid hangs.
dominion.once('shutdown', function () {
    var killtimer = setTimeout(function () {
        process.exit(1);
    }, 5000);

    killtimer.unref();
});


// Create a server.
var server = http.createServer(function (req, res) {
    'use strict';

    dominion.vanilla(req, res);

    // Other handler logic...
});

// Register the server with dominion.
dominion.addServer(server);

server.listen(3000);

You should register all servers with dominion. If any exceptions are generated by a request or a response, then all registered servers are closed to stop new incoming connections. You should register a listener on the 'shutdown' event to for the server to close after some time, in case the server hangs.

Methods

dominion.middleware(req, res, next)

This is a traditional express middleware. If an error is caught by the domain, then it attempts to send a 500 response and close all registered servers.

dominion.vanilla(req, res)

This behaves much like the middleware, but is intended for use with vanilla Node HTTP servers. Place at the top of your response handler.

dominion.addServer(server)

Add the HTTP server object to the dominion module. All registered servers will be closed if dominion intercepts an error. Since dominion will shut down all servers before quitting the worker process, all should be registered. On a cluster worker, all servers will be closed whether of not they have been registered.

Events

Events for logging and shutdown are emitted by dominion. It is assumed that you'll have your own logging solution.

shutdown: (request, response, error, sendError)

Emitted when the domain inside the middleware catches an error. You should register a listener on this event to set a timeout to force the process to close if it is hung for whatever reason. Listeners will receive the arguments:

  • request - The request object.
  • response - The response object.
  • error - The error caught by the domain middleware.
  • sendError - This will be defined only if an error occurs when trying to send a response.