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

@dset/utils

v1.0.0

Published

DSET platform utilities (Layer: utils) — pure, framework-agnostic formatting, status-mapping, chart and CSV helpers. Zero React, zero UI, zero business logic.

Downloads

62

Readme

@dset/utils

Pure, framework-agnostic platform utilities. Zero React, zero UI, zero business logic — every export is a deterministic function (the one exception, a CSV download, is a clearly-marked browser side-effect wrapper around a pure toCsv).

Layer rule: utils may import no other @dset/* package. It is the leaf of the dependency graph, alongside @dset/tokens.

What's here

| Area | Exports | Source pattern | | -------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | | Currency | formatCurrency, formatLakh | i3MS formatters.js | | Number | formatNumber, formatPercent, formatWeight | i3MS inline WT/% patterns (consolidated) | | Date | formatDate, formatDateShort, formatDateTime, formatDateRange, normalizeDates | i3MS formatters.js + dates.js | | Financial year | currentFY, fyToDateRange | i3MS formatters.js (Indian Apr–Mar FY) | | Status mapping | mapStatus, createStatusMapper | i3MS inline STATUS_LABEL/STATUS_VARIANT (pattern only — domain map injected) | | Charts | CHART_COLORS, CHART_SERIES, chartColor | i3MS chartColors.js | | CSV | toCsv, csvCell, downloadRowsAsCsv | i3MS csv.js |

Usage

import { formatCurrency, mapStatus, chartColor } from '@dset/utils';

formatCurrency(1234567); // "₹12,34,567"
formatCurrency(1234567, { lakh: true }); // "₹12.35 L"

const STATUS = { paid: { label: 'Paid', variant: 'success' } };
mapStatus('paid', STATUS).variant; // "success"  (feed to @dset/ui <Badge>)

chartColor(0); // "#0ea5e9"

Design notes

  • Locale is injectable. Formatters default to en-IN (DSET's first market) but accept a locale/currency so they generalize to any product.
  • Status mapping is pattern, not data. The domain status map stays in the product; this package only resolves a value against it with a typed fallback.
  • Chart hex lives here, deliberately. <canvas> cannot read CSS custom properties, so the chart palette ships as literal hex — the source-of-truth that --dset-color-chart-* tokens mirror. Keep them in sync.

Deferred (audited, not yet proven)

formatINR (covered by formatCurrency), per-route status enums (domain-specific, stay in product), handleCsvDownload (coupled to i3MS extraction service).