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

clacks

v0.0.0

Published

http/url path router

Readme

Clacks

Clacks is a simple HTTP/URL path router for the Node.js HTTP Server.

Installation

npm install clacks

Usage

var Clacks = require("clacks");
var http = require("http");

var app = new Clacks();

app.get("/", function(req, res) {
    res.end("Hello world!");
});

app.get("/examples/:exampleID", function (req, res) {
    res.end(req.path.exampleID);
});

http.createServer(app.dispatcher).listen(9292, "127.0.0.1");

Clacks()

Constructor

var app = new Clacks();

app.add(path, handler[, method])

Set up a handler for path and method.

handler should be a function, path a rails/sinatra-style url path, and method an uppercased HTTP method. If method is omitted, handler will be invoked whenever path matches, regardless of the HTTP method.

app.add("/foo", function (req, res) {
    res.end("you requested /foo with GET");
}, "GET");

app.add("/bar", function (req, res) {
    res.end("you POSTed to /bar");
}, "POST");

app.add("/baz", function (req, res) {
    res.end("/baz doesn't care what method you use");
});

handler will be called with two arguments, a request object and a response object. These are the standard Node.js HTTP server request and response objects. The request object has an additional 'path' attribute, which is an object holding path variables.

app.add("/users/:userID", function (req, res) {
    res.end("you asked for user " + req.path.userID);
});

app.head(path, handler)

Shortcut for app.add(path, handler, "HEAD").

app.get(path, handler)

Shortcut for app.add(path, handler, "GET").

app.post(path, handler)

Shortcut for app.add(path, handler, "POST").

app.put(path, handler)

Shortcut for app.add(path, handler, "PUT").

app.del(path, handler)

Shortcut for app.add(path, handler, "DELETE").

app.patch(path, handler)

Shortcut for app.add(path, handler, "PATCH").

app.notFound(req, res)

Invoked when no handler is found. It is unlikely you will need to call this function, but you can set the notFound property of your app to a custom function to implement your own not found handler.

app.dispatch(req, res)

Dispatch req and res to the appropriate handler. You're unlikely to need to call this function directly, though it may come in handy when testing or debugging.

app.dispatcher

Dispatcher function bound to app. Indented to be handed to http.createServer.