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

@pirxpilot/server-timings

v2.0.0

Published

Adds `Server-Timings` header

Readme

NPM version Build Status Dependency Status

@pirxpilot/server-timings

This is a modernized fork of server-timings

Usage

Load the middleware as early as possible to record the request timing:

import express from 'express';
import timings from 'server-timings';
import routes from './routes.js';

const app = express();

app.use(timings);
app.use(routes);

This will automatically add a Server-Timing header shown in milliseconds.

$ curl https://jsonbin.org/remy/urls -I
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Server-Timing: total; dur=72.45

To include additional timings the middleware exposes two methods on the res.locals.timings property:

  • start(label[, description]) - record the start time
  • end(label) - end the record time - if this isn't called, it will be called when the request is finished

Start/end as middleware

As well as being exposed in res.locals.timings you can also call start and end as middleware:

import timings from 'server-timings';
import routes from './routes.js';

app.use(timings);
app.use(timings.start('routing'));
app.use(routes);
app.use(timings.end('routing'));