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 🙏

© 2025 – Pkg Stats / Ryan Hefner

waymaker

v0.1.0

Published

An Express Middleware That Routes Based On Domain

Readme

Waymaker: An Express Middleware That Routes Based On The Request

Waymaker is currently centered around routing based on domain name, but that is likely to change as the package expands. This is due to the fact that Waymaker has no explicit reason for only resolving based on domain.

WARNING

NodeJS must be v12 or higher, as this library does use private fields and arrow functions.

Example

Eventually, I'll write full documentation for Waymaker, but for now this will do.

Create a project and add express and waymaker.

Create app.js and paste the following code block.

const express = require("express");
const app = express();
const port = 80;

const Waymaker = require("waymaker");

const waymaker = new Waymaker({
    matcher: Waymaker.matchers.SubdomainMatcher,
    match: { baseDomain: "localhost" },
});

const hiRouter = express.Router();

hiRouter.get("/", (req, res) => {
    res.send("Hi!");
});

const byeRouter = express.Router();

byeRouter.get("/", (req, res) => {
    res.send("Bye!");
});

waymaker.register("hi", hiRouter);

waymaker.register("bye", byeRouter);

app.use(waymaker.middleware);

app.listen(port, () => {
    console.log(`Example app listening on port ${port}`);
});

Now run the app.js.

When you visit hi.localhost in your browser you should see hi.

When you visit bye.localhost in your browser you should see bye.