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

ms-util

v0.1.2

Published

Convert milliseconds to something useful

Downloads

7

Readme

Build Status Coverage Status

NPM

Converting millis to a human-readable string is a pain. It doesn't have to be.

Table of contents

Related packages

You might want to check out the ms package. There are two main differences:

  • It can convert a string to millis
  • It can't display more than one unit, i.e. 3,660,000 ms would be converted to one hour, not one hour and one minute.

Base usage

Note: play around with it on Runkit!

Browser

It's always best to use a specific version - you'll find the CDN URLs here.

<script src="https://cdn.jsdelivr.net/ms-util/latest/ms-util.min.js" type="application/javascript"></script>
<!-- It is now available as window.parseMs -->

NodeJS

const parseMs = require('ms-util');

API

parse

Parse the given millis and return the number of days, hours, minutes seconds and ms they translate to.

console.log(parseMs.parse(86407049));
{
    "days": 1,
    "hours": 0,
    "minutes": 0,
    "seconds": 7,
    "millis": 49,
    "input": 86407049
}

toWords

Parse the given millis to a word string, e.g. 3660000 ms would become 01hr 01min 00sec by default.

Function signature:

parseMs.toWords = (ms, cfg = {}) => {};

Where ms is the millis you want to convert and cfg is configuration with the following keys:

  • pad: Whether to pad numbers with zeroes or not. Default: true.
  • forceMS: Force displaying millis even if ms is >= 1000. Default: false.
  • lang: Language pack override. The default is:
{
    "ms": "ms",
    "sec": "sec",
    "min": "min",
    "hour": "hr",
    "day": "d"
}

Usage:

console.log(parseMs.toWords(86407049)); // 1d 00hr 00min 07sec

colonSeparated

Parse the given millis to a colon-separated string, e.g. 3660000 ms would become 01:01:00 by default

Function signature:

parseMs.colonSeparated = (ms, cfg = {}) => {};

Where ms is the millis you want to convert and cfg is configuration with the following keys:

  • pad: Whether to pad numbers with zeroes or not. Default: true.
  • forceMS: Force displaying millis even if ms is >= 1000. Default: false.

Usage:

console.log(parseMs.colonSeparated(86407049)); // 1:00:00:07