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

freeze-clock

v1.0.0

Published

Freeze Date and drive setTimeout/setInterval in tests — tiny, zero-dependency fake clock.

Readme

freeze-clock

Freeze Date and drive setTimeout / setInterval yourself — a tiny, zero-dependency fake clock for tests.

No Sinon. No Jest. Just install, tick, uninstall.

import { install, uninstall } from "freeze-clock";

const clock = install({ now: "2024-01-01T00:00:00.000Z" });

setTimeout(() => console.log("done", Date.now()), 1000);
clock.tick(1000); // → "done" 1704067201000

uninstall();

Install

npm install freeze-clock

Usage

Basic

import { install } from "freeze-clock";

const clock = install({ now: 0 });

assert.equal(Date.now(), 0);

let fired = false;
setTimeout(() => {
  fired = true;
}, 500);

clock.tick(499);
assert.equal(fired, false);

clock.tick(1);
assert.equal(fired, true);
assert.equal(Date.now(), 500);

clock.uninstall();

With node:test / any runner

import { afterEach, test } from "node:test";
import { install, uninstall } from "freeze-clock";

afterEach(() => uninstall());

test("retries after a backoff", () => {
  const clock = install({ now: Date.parse("2024-06-01") });
  // ... schedule work that uses setTimeout / Date ...
  clock.tick(5_000);
});

API

install(options?)Clock

Patches Date, setTimeout, clearTimeout, setInterval, clearInterval, and (by default) performance.now.

| Option | Default | Description | | --- | --- | --- | | now | real now | Initial fake time (number, ISO string, or Date) | | toFakePerformance | true | Also patch performance.now | | loopLimit | 10000 | Max timer firings per tick / runAll (infinite-loop guard) |

Throws if a clock is already installed.

uninstall()boolean

Restores the real globals. Returns whether a clock was active.

getClock()Clock | null

The currently installed clock, if any.

Clock methods

| Method | Description | | --- | --- | | now | Current fake epoch ms (getter) | | tick(ms) | Advance ms, firing due timers in order | | next() | Fire the next timer only; returns ms advanced (or undefined) | | runAll() | Fire every pending timer (including ones scheduled during the run) | | runToLast() | Advance to the last timer that existed when called | | setSystemTime(time) | Jump the clock without firing timers | | countTimers() | Pending timer count | | clearAll() | Cancel every pending timer | | uninstall() | Restore globals |

How it behaves

  • Timers fire in due-time order; ties break by schedule order.
  • Timeouts scheduled during a tick fire in the same tick if still due.
  • setInterval keeps a fixed cadence from its previous due time.
  • Date.parse / Date.UTC stay real; only “current time” is faked.
  • performance.now() starts at 0 on install and tracks tick.

License

MIT