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

timestring-unit

v0.1.2

Published

Time string conversion

Downloads

6

Readme

Time string conversion library

This library is used for converting time strings, e.g. 1 month, to an integer value relative to another unit.

Example

const tsUnit = require('timestring-unit');

tsUnit.parse('1 hour'); // 3600000
tsUnit.parseTo('1 hour', 'ms'); // 3600000
tsUnit.parseTo('1 minute', 'ms'); // 60000
tsUnit.parseTo('1min', 'ms'); // 60000
tsUnit.parseTo('1h 1min', 'ms'); // 3660000

API

You can require the module in several ways:

Default

const tsUnit = require('timestring-unit');

tsUnit.parseTo('1 hour'); // 3600000
tsUnit.parseTo('1 hour', 's'); // 3600
tsUnit.parseTo('1h 1min', 'ms'); // 3660000

Prototype

Modifies the String prototype. NOT RECOMMENDED

const tsUnit = require('timestring-unit/prototype');

'1 hour'.toTime(); // 3600000
'1 hour'.toTime('s'); // 3600
'1h 1min'.toTime('ms'); // 3660000

Tag

Using the custom interpolation feature of ES6:

const tsUnit = require('timestring-unit/tag');

tsUnit `1 hour`; // 3600000
tsUnit `${'s'} 1 hour`; // 3600
tsUnit `1h 1min ${'ms'}`; // 3660000

What for?

This library was created because I was sick of having a mix of millisecond-based and second-based integer values in my configuration files. For example, using Redis EXPIRE (which uses seconds) and setTimeout in the same project, you get a config file that looks like this:

// config.js
module.exports = {
  redis: {
    defaultTtl: 1,
  },
  stuff: {
    sleepTime: 1000,
  },
};

Which uses which unit?

Instead, with this library, you can have this:

// config.js
const tsUnit = require('timestring-unit/tag');
module.exports = {
  redis: {
    defaultTtl: tsUnit `1s ${'s'}`,
  },
  stuff: {
    sleepTime: tsUnit `1s ${'ms'}`,
  },
};

I find this more explicit.

You could also defer the unit conversing when calling the library, keeping only strings in your configuration file:

// config.js
module.exports = {
  redis: {
    defaultTtl: '1s',
  },
  stuff: {
    sleepTime: '1s',
  },
};


// redis.js
const tsUnit = require('timestring-unit');
module.exports.setTtl = async (key, ttl) => {
  return await whicheverRedisClient.exec(`EXPIRE ${key} ${tsUnit.parseTo(ttl || config.defaultTtl, 'ms')}`);
};

And BAM! unit conversion isn't tied to your configuration anymore, only where it's appropriate.

Note that I don't recommend this method because it may impact performance. You should rather "compile" your strings beforehand, at least for non-variable ones.