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

human-unit

v2.0.1

Published

Unit formatter for human

Downloads

95

Readme

human-unit

Unit formatter for human

Build Status NPM Version

Install

npm install human-unit

Usage

- File size

import humanUnit, {sizePreset} from 'human-unit'
humanUnit(1024, sizePreset)  // {value: 1, unit: 'KB'}
humanUnit(1024, {unit: 'MB', ...sizePreset})  // {value: 1, unit: 'GB'}
// change units as you need
humanUnit(1024, {
    unit: 'M',
    units: ['M', 'G'],
    factors: [1024]
})
// {value: 1, unit: 'G'}

- Time unit

import humanUnit from 'human-unit'
const timePreset = {
    factors: [1000, 60, 60, 24],
    units: ['mili', 'sec', 'min', 'hour', 'day']
}
humanUnit(18000, {unit: 'sec', ...timePreset})  // {value: 5, unit: 'hour'}
humanUnit(60000, timePreset)  // {value: 1, unit: 'min'}

API

humanUnit(value: number, options?:IOptions)

return { value: number; unit: string; }

interface IOptions {
    unit?: string | undefined,
    units?: string[];  // array of units, must contain unit arg
    factors?: number | number[]; // factor for All/Each units
    ceils?: number | number[];  // ceil for All/Each units
}

The factors is the divider when bumpping units levels, can be a fixed number like in file size of 1024, or can be array of numbers like in time units.

The ceils value will be used to determine whether the unit should be bumped into next level, say, ceils: [10240], will allow the result: {value: 10000, unit: 'MB'}, better for human control.

Note

The file size calculation is easy if you look into the rule, I want to use SI standard when below GB, so the units is B,KB,MB,GB (notice the KB is not kB), but when the size is very big, after GB I want to use IEC standard, this is why the factors is array of numbers by default that changed from 1024 to 1000 after GB.