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

@awsless/duration

v0.0.4

Published

The @awsless/duration package provides utility functions for handling & readable duration values in API's.

Readme

@awsless/duration

The @awsless/duration package provides utility functions for handling & readable duration values in API's.

The Problem

API designers traditionally have two choices when modeling an duration values. Imagine the follow ttl prop inside an API.

type API = {
	ttl: number
}

The problem with this design is that it's not clear what unit the ttl prop is without reading the docs.

A way around this issue is to include the unit inside the prop name.

type API = {
	ttlInSeconds: number
}

The problem with this design is that it's overly verbose. But even more importantly in both examples the API consumer can't easily pass in values in unit's other then seconds. Imagine providing the API an ttl of 1 week.

api({
	ttl: 60 * 60 * 24 * 7
})

The Solution / Basic Usage

Defining your API

import { toSeconds, Duration } from '@awsless/duration';

type Props = {
	ttl: Duration
}

const api = (props: Props) => {
	// When using a duration type you need to cast it to a spesific unit.
	// In this example we want the ttl in seconds.
	const ttl = toSeconds(props.ttl)
}

Consuming your API

import { weeks } from '@awsless/duration';

// Even tho the ttl is used in seconds, we can still pass in any duration unit we want.
api({ ttl: weeks(1) })

String Parsing

We also expose an parse function to parse a string representation of a duration value.

import { parse } from '@awsless/duration';

const duration = parse('1 day')