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

relay.ts

v1.0.1

Published

Performant webserver framework with a familiar API

Downloads

21

Readme

relay.ts

Serve RESTFul APIs quickly and simply

What?

This project is an abstraction over the builtin HTTP(s) module in Node. It aims to emulate the Express.js API, whilst being very performant and almost entirely dependency free.

Currently, this library is in very early stages and used more as a learning experience.

How does this differ from Express?

Express is based on Connect, which has the simple concept of: all middleware goes on a central stack. The stack of middleware is traversed and checking verb/url.

In relay, the .init() method organises middle in to different stacks, accessed via an object with the URL as a key. Each URL sits under each verb, which is the key, too:

this.middlewares = {
  'GET': {
    '/': [Middleware, Middleware],
    '/api': [Middleware, Middleware],
    '*': [Middleware]
  },
  'POST': {
    '/api': [Middleware]
  }
}

As you can guess, middleware lookup is O(1), not O(N) worst case. PERF

Usage

Once this is published on npm, install it!

yarn add ${libname}

Then, create a server!

import path from 'path';
import relay, { useStatic } from 'relay';

const server: Server = relay.createServer({ port: 8080 });

// you can use HTTP verbs, and use - just like express!
server.get('/', (req, res) => {
  res.send('hello, world');
});

// static file hosting built in:
server.get(useStatic(path.join(__dirname, 'static')));

// you can also chain!
server.get('/baz', (req, res, next) => {
  delete req._req;
  res.json(req);
})
.post('/', (req, res) => {
  res.send('oi')
});

// make sure to call .init, to create the server!
server.init().then(() => console.log('listening on 8080'));

Roadmap:

  • [x] Body parsing (form, json, urlencoded)
  • [x] HTTP Verbs support
  • [x] query param parsing
  • [x] next() (very fucking difficult)
  • [ ] cookie parsing (sort of works)
  • [x] use middleware
  • [x] Static files
  • [ ] Compression (gzip + ???)