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 🙏

© 2024 – Pkg Stats / Ryan Hefner

hdinf

v1.0.4

Published

Parses duration information from human-readable format into an arbitrary format.

Downloads

1,856

Readme

hdinf

hdinf (human-duration in format) parses duration information from human-readable format into an arbitrary format.

Motivation

The frustration of seeing code littered with 86_400 and 60 * 60 * 24 and similar expressions.

Usage

import {
  getDuration,
  type HumanDuration,
  type IntervalName,
} from 'hdinf';

// parseDuration(duration: HumanDuration, interval: IntervalName): number
getDuration('1 day', 'seconds');
getDuration('1 day 2 hours 3 seconds', 'milliseconds');

In the wild, you should use this library remove any hard-coded durations from your codebase, e.g.,

- setTimeout(() => {}, 86_400);
+ setTimeout(() => {}, getDuration('1 day', 'seconds'));

Similarly, anywhere where you define inputs for a function, you should consider using HumanDuration instead of a raw number in an arbitrary format, e.g.,

- const foo = (durationInSeconds: number) => {}
+ const foo = (duration: HumanDuration) => {}

This will reduce the number of bugs that are introduced by passing in a duration in the wrong format.

TypeScript

One of the benefits of this library is that the input format is enforced using TypeScript template literal types, i.e. the compiler will complain if you pass in an invalid duration.

import { getDuration } from 'hdinf';

getDuration('1 day', 'seconds'); // OK
getDuration('1 day', 'milliseconds'); // OK
getDuration('1 day', 'minutes'); // OK
getDuration('1 day', 'hours'); // OK

getDuration('1 foo', 'seconds'); // TS error because foo is not a valid time period
getDuration('1 hour 1 day', 'seconds'); // TS error because lesser units cannot precede greater units (hour < day)

Abbreviations

Abbreviations are intentionally not supported. The goal of this library is to reduce the variations in how durations are expressed.

Alternatives

hdinf was primarily designed with the intent of replacing the use of constants rather than allowing dynamic expressions.

dayjs

If you are already using a library like dayjs, you can probably find a native solution for this problem, e.g.,

import dayjs from 'dayjs';
import duration from 'dayjs/plugin/duration';

dayjs.extend(duration);
dayjs.duration(100, 'days');

ms

My grudge with ms is that:

  • it allows arbitrary formats (so you end up with 1ms, 1msec, 1millisecond, etc)
  • it only allows to express output in milliseconds, so you end up with / 1000 and similar expressions