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

hurt

v0.1.0-alpha.1

Published

HTTP and SPA routing using RFC 6570 URI templates

Downloads

4

Readme

hurt

HTTP routing with URI templates

After all of two minutes browsing npmjs.org I could not find what I was looking for, so I built it myself. How hard can it be, right?

Motivation

Not very. RFC 6570 specifies URI templates, of which there are a bunch of very nice implementations. However, at the time of writing, full featured URI template routers for express, connect or restify were hard to come by.

So what's so great about URI templates then? For one, they have a syntax to properly describe recursive paths and arguments. This makes them great for describing APIs. Actually, you might have seen them, for example in GitHubs API documentation. Also, when you're writing a RESTful API you'll often write URLs into your service's responses. Instead of hard-coding the URLs or using some other way to generate them, you can just use the router to give you a route, because if any part of your software knows which URLs are reachable, it's your router.

Usage

So what does hurt look like? Glad you asked! Let's start this of with an example:

import hurt from 'hurt';
import { Users } from './app/model';

const router = hurt();

router.get('/users/{name}', function (req, res, next) {
  const { name } = req.params;
  const user = Users.get({ name });
  res.send(200, user);
});

router.get('/users{?q,page}', function (req, res, next) {
  const { q, page = 0 } = req.params;
  const length = 10;
  const start = page * length;
  const users = Users.find({ q }).slice(start, length);
  res.send(200, users);
});

Just like so many other routers, except with RFC 6570 URI templates. There are some nice bonuses though. Check out the docs.

Installation

npm

npm install hurt

bower

bower install hurt

html

curl -o hurt.min.js https://github.com/jpommerening/hurt/releases/download/v0.1.0/hurt.min.js
echo '<script src="hurt.min.js"></script>' >> index.html