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

wildcard-subdomains

v1.1.0

Published

Handle dynamic/wildcard subdomains in Express.js

Downloads

405

Readme

wildcard-subdomains

Build Status npm version

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

Requests to foo.yourdomain.com can be handled with using the route /_sub/:subdomain

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

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

Dependency free!

How to use

Require the module in app.js:

var wildcardSubdomains = require('wildcard-subdomains')

Use the module in middleware:

app.use(wildcardSubdomains(opts))

opts - Object

| Key | Type | Default | Description | | --------- | --------------- | -------- | ---------------------- | | namespace | String | '_sub' | Prepended to the path | | whitelist | String or Array | ['www']| Subdomains to ignore |

Example options:

app.use(wildcardSubdomains({
  namespace: 's',
  whitelist: ['www', 'app'],
}))

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

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

By using the whiteList option, requests to app.yourdomain.com and www.yourdomain.com will be ignored and handled normally.

Example

npm run example

Or check the examples directory in this repo

Protip

For testing subdomains locally, use the domain vcap.me:3000

This is a domain that points back to your localhost, allowing you to test subdomains like foobar.vcap.me

Running your app behind a proxy? You'll likely need to set the appropriate trust proxy in express