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

metriqa

v0.1.0

Published

Measurement units management made easy and well-typed

Readme

metriqa

Measurement units management made easy and well-typed :sparkles:

Installation

npm i metriqa

Usage

First of all, import the needed functions from the library:

import { unit, measurement } from 'metriqa'

Second, define a measurement. For demonstration purpose, let's define a measurement for information:

const information = measurement(
  unit('bit'), // the base measurement unit
  unit('byte', 8), // this number represents how many bits are in a byte
  unit('kibibyte', 1024), // ... how many bytes are in a kibibyte
  unit('mebibyte', 1024), // ... how many kibibytes are in a mebibyte
  // and so on
)

And finally, we can define some quantity of or measurement and convert in back and forth!

const _512bytes = information(512, 'byte')

_512bytes.in('bit') // 4096
_512bytes.in('kibibyte') // 0.5

Notice that this API is well-typed. Whenever you type _512bytes.in( TS will infer the type of the argument as 'bit' | 'byte' | 'kibibyte' | 'mebibyte' | ...

There is also a toString method of a quantity:

const _512bytes = information(512, 'byte')

_512bytes.toString() // 512 byte
_512bytes.toString('bit') // 4096 bit

Contributing

Please feel free to open issues and pull requests in any form.

Build

npm run build

Test (using vitest)

npm run test