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

time-machine-js-plugin-express

v1.1.0

Published

Express middleware for time-machine-js

Readme

time-machine-js-plugin-express

An Express.js middleware plugin for time-machine-js. It allows you to easily manipulate the global server time globally via environment variables or on a per-request basis using HTTP headers.

Installation

npm install time-machine-js-plugin-express

Usage

1. Global Initialization via Environment Variable

You can automatically set the server's time upon initialization by reading from the TIME_MACHINE_TRAVEL_TO environment variable.

Make sure your environment variable is set before your app starts:

# .env
TIME_MACHINE_TRAVEL_TO="2020-01-01T00:00:00Z"

Then initialize it in your code:

import { initTimeMachineFromEnv } from "time-machine-js-plugin-express";

// Initialize with a preferred mode ('flowing' or 'frozen')
initTimeMachineFromEnv({ mode: "flowing" });

2. Per-Request Time Travel via Middleware

You can allow clients to travel to a specific time for the duration of a single HTTP request using a custom header. The middleware automatically handles reverting the time back to its previous state after the request finishes.

import express from "express";
import { timeMachineMiddleware } from "time-machine-js-plugin-express";

const app = express();

// Use the middleware globally or on specific routes
app.use(
  timeMachineMiddleware({
    // Optional: customize the header name (default is 'x-time-traveled-to')
    headerName: "x-time-traveled-to",
  }),
);

app.get("/current-time", (req, res) => {
  res.json({ time: new Date().toISOString() });
});

app.listen(3000, () => console.log("Server running on port 3000"));

Testing the request:

curl -H "x-time-traveled-to: 1999-12-31T23:59:59Z" http://localhost:3000/current-time
# Output will reflect the traveled time

Concurrency Note for Node.js

Because time-machine-js patches Date.now() globally, Node.js applications that process multiple requests concurrently may experience side-effects where one request's modified time bleeds into another request running at the exact same time. This plugin is most optimal for development, testing, and staging environments.

License

MIT