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 🙏

© 2026 – Pkg Stats / Ryan Hefner

domain-api

v1.0.3

Published

Handle dynamic domains in Express.js. Perfect for when you have customized domains for different users, and need to handle them within your Node app.

Readme

domain-api

Handle dynamic domains in Express.js. Perfect for when you have customized domains for different users, and need to handle them within your Node app.

Requests to foo.com can be handled with using the route /domain/:domain

Paths and query strings and paths remain intact. For example:

foo.com/post/cat?oh=hai can be handled with using the route /domain/foo.com/post/cat?oh=hai

Installation

npm install domain-api --save

usage

Require the module in app.js:

var domain = require('domain-api')

Use the module in middleware:

app.use(domain(opts))

options

| Key | Type | Default | Description | | ------------- | ------------- | -------- | ---------------------- | | namespace | String | 'domain' | Prepended to the path | | excludeDomain | String/Array | [] | Ignore domain |

Example options:

var domain = require('domain-api');
app.use(domain({
  namespace: 's',
  excludeDomain: 'mydomain.com',
}))

Handle the new route for your domain, for example foo.com would be handled with:

app.get('/s/foo.com/', function(req, res){
  res.send("Meow!")
})