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

strict-timeout

v1.1.0

Published

setTimeout which throws instead of misbehaving with huge delays

Downloads

637

Readme

strict-timeout

Package Version License PackagePhobia Node compatibility

setTimeout() that throws instead of misbehaving with large delays

A value larger than 2147483647 milliseconds (~25 days) is too large to fit into a signed 32-bit integer, which is not supported by some JS engines, which will silently use 1 millisecond instead.

Such a surprising behavior is a very bad idea and has caused me issues a couple of times.

This module exports a small wrapper around setTimeout which will throw a RangeError if the specified delay is above this value.

Install

> npm install strict-timeout

Compatibility

Should be compatible with pretty much anything that provides a global setTimeout and clearTimeout:

Usage

The API is exactly the same as native setTimeout and the returned result can be used with native clearTimeout, the only difference is that it will throw if the delay is too big.

const strictTimeout = require("strict-timeout");

const handle = setTimeout(callback, delay, arg1, arg2);

safeTimeout

This module also provides a safe version of setTimeout which will correctly behave with huge delays.

As for strictTimeout, the API is the same as native setTimeout, but you cannot use native clearTimeout for this one, you must use safeTimeout.clear() instead:

const safeTimeout = require("strict-timeout/safe");

const handle = safeTimeout(callback, delay, arg1, arg2);

// Node `ref` and `unref` methods are available
handle.unref();
handle.ref();

// you cannot use native clearTimeout!
safeTimeout.clear(handle);

License

ISC © Julien Fontanet