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

@quantities/registry

v1.0.0

Published

Custom registry support for @quantities/core

Downloads

184

Readme

@quantities/registry

Custom unit registries for @quantities/core. Define your own units and prefixes, then get a Quantity constructor bound to them.

Install

npm install @quantities/registry
bun add @quantities/registry

Defining units

A unit is a UnitEntry (type from @quantities/core). numerator references the base unit(s) it derives from; omit it to declare a new base unit.

import type { UnitEntry } from "@quantities/core";

const cubit: UnitEntry = {
	key: "<cubit>",
	aliases: ["cubit", "cubits"],
	scalar: 0.4572,
	kind: "length",
	numerator: ["<meter>"],
};

Building a registry

createRegistry(units?, source?) returns a new UnitRegistry. It accepts a single entry, an array, or an array of arrays. By default it extends core's DEFAULT_REGISTRY; pass null as source to start from an empty registry.

import { createRegistry, withRegistry } from "@quantities/registry";

const registry = createRegistry(cubit); // core units + cubit

withRegistry(registry) returns a Quantity constructor (plus getUnits / getAliases helpers) scoped to that registry. Destructure default to name it:

const { default: Quantity, getUnits } = withRegistry(registry);

Quantity("2 cubits").to("m").format(); // → "0.9144 m"
getUnits("length"); // → includes "cubit"

Quantities from different registries cannot interoperate — operate only within the constructor returned by withRegistry.

Adding prefixes

A prefix is just a UnitEntry with kind: "prefix" and no decomposition — pass it to createRegistry exactly like any unit:

const withGoogol = createRegistry(
	{
		key: "<googol>",
		aliases: ["googol"],
		scalar: 1e100,
		kind: "prefix",
	},
	registry,
);

Validation

Entries are validated automatically when added (scalars, references, alias collisions, and dependency cycles). The individual validators are also exported for standalone use:

import {
	validateUnitEntry,
	validatePrefixEntry,
	validateScalar,
	validateReferences,
	checkUnitAliasCollisions,
	checkPrefixAliasCollisions,
	detectCycles,
} from "@quantities/registry";

Specialized units

@quantities/units provides ready-made, kind-grouped definitions you can pass straight to createRegistry.

License

MIT