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

@deltic/clock

v0.1.0

Published

Be in control of time.

Readme

@deltic/clock

Make your codebase, and especially tests, more deterministic by encapsulating time. Stop fuzzy matching, use exact matching instead by fixating the random nature of time.

Installation

npm i -S @deltic/clock
# or
pnpm add @deltic/clock

Usage

While (date)time is global in JavaScript environments, being tied to non-deterministic global state causes many issues. The clock package is designed to remove this source of issues by encapsulating time. There is some cost associated with using this over using global Date functionality, but the benefits largely outweigh the cost.

The package consists of three parts:

  1. An interface for consumers to depend on.
  2. A system-clock implementation that gives real time.
  3. A test-clock implementation for controlling time in tests.

The Clock interface:

The interface consists of the following methods:

  • now(): number – an equivalent of Date.now()
  • date(): Date – an equivalent of new Date()

Consuming time

There are two modes of consuming time; by injection or by using the GlobalClock.

Whenever when using injection, depend on the Clock interface:

import type {Clock} from '@deltic/clock';

class MyService {
    constructor(
        private readonly clock: Clock,
    ) {
    }

    timestamp(label: string): string {
        return `${label}-${this.clock.now()}`;
    }
}

Or, use the globally available clock:

import {GlobalClock} from '@deltic/clock';

function timestampLabel(label: string): string {
    return `${label}-${GlobalClock.now()}`;
}

Fixating time in tests

In tests, the GlobalClock is an instance of the TestClock. The GlobalTestClock is the same instance, but allows you to manipulate time.

The TestClock methods are:

  • tick(): void – to advance one ms
  • advance(increment: number): void – to advance with N amount of ms,
  • travelTo(laterTime: number | string): void – to set the clock to a particular point in time

See it in action:

import {createTestClock, GlobalTestClock} from '@deltic/clock';
import {timestampLabel} from './timestamp-label.js';

describe('functionality', () => {
    test('it works', () => {
        const clock = createTestClock(); // or use GlobalTestClock
        const now = clock.now();

        expect(timestampLabel('label')).toEqual('label-${now}');
    });

    test('it works with a set timestamp', () => {
        const now = 1500_000_000_000;
        const clock = createTestClock(now); // or use GlobalTestClock

        expect(timestampLabel('label')).toEqual('label-1500000000000');
    });
});