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

kiss-router

v1.2.0

Published

A stupid simple browser routing library

Readme

KISS Router

KISS router is a really stupid simple 'routing' option for use in javascript apps. It's designed to have a really simple API and to be used with whatever history management system you like.

The api consists of one function: createMatcher, which takes an array of routes, and returns a 'matcher' function that will match a Location object to a route. When a match is found, an object is returned with the route name, the route and query parameters, and any additional keys specified in the route definition.

Here's an example of it in use:

import createMatcher from 'kiss-router';

const matcher = createMatcher([
  { name: 'HOME', path: '/' },
  { name: 'POSTS', path: '/posts' },
  { name: 'NEW_POST', path: '/posts/new' },
  { name: 'POST', path: '/posts/:id' },
  { name: 'SEARCH', path: '/search' }
]);

const match1 = matcher({ pathname: '/posts/123', search: '' });
console.log(match1) // { route: 'POST', params: { id: '123' } }

const match2 = matcher({ pathname: '/posts/new', search: '' });
console.log(match1) // { route: 'NEW_POST', params: {} }

const match1 = matcher({ pathname: '/search', search: '?q=hello' });
console.log(match1) // { route: 'SEARCH', params: { q: 'hello' } }

To actually use this library in an app, it should be subscribed to history changes, and the resulting match should be used to render the corresponding page, like so:

import createBrowserHistory from 'history/createBrowserHistory';
import createMatcher from 'kiss-router';

const history = createBrowserHistory();

const matcher = createMatcher([
  { name: 'HOME', path: '/' },
  { name: 'POSTS', path: '/posts' },
  { name: 'NEW_POST', path: '/posts/new' },
  { name: 'POST', path: '/posts/:id' },
  { name: 'SEARCH', path: '/search' }
]);

const render = (location) => {
  const match = matcher(location);

  if (!match) return render404();

  switch (match.route) {
    case 'HOME': return renderHome();
    case 'POSTS': return renderPosts(match.params.page || 1);
    case 'NEW_POST': return renderNewPost();
    case 'POST': return renderPost(match.params.id);
    case 'SEARCH': return renderSearch(match.params.q);
  };
}

history.listen((location) => {
  render(location);
})