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

@gomani/i18n

v0.8.0

Published

Inclusion by default: ICU messages, locale-aware formatting, locale routing, and full RTL/bidi support.

Readme

@gomani/i18n

Inclusion by default (P11): ICU messages, locale-aware formatting, locale routing, and full RTL/bidi — with the active locale resolved server-side, per request, zero-JS.

Locale is a signal (like network quality in @gomani/adaptive): @gomani/server resolves it from the request — a URL locale prefix, the gomani-locale pin cookie, Accept-Language, then the default — before the synchronous render, so only the chosen language's strings and the correct dir reach the HTML. No client i18n runtime, no flash of the wrong language.

import { createI18n } from '@gomani/i18n';

export const { t } = createI18n({
  locales: ['en', 'sw', 'ar'],
  defaultLocale: 'en',
  messages: {
    en: { items: '{n, plural, one {# item} other {# items}}' },
    sw: { items: '{n, plural, one {kitu #} other {vitu #}}' },
    ar: { items: '{n, plural, one {# عنصر} other {# عناصر}}' },
  },
});

t('items', { n: 3 }); // locale-correct plural, formatted with Intl
  • ICU MessageFormat — arguments, number/date/time with styles, plural/selectordinal (offset:, =N, #), select, nesting, and apostrophe quoting. Plural/number/date selection uses the platform Intl (present everywhere, zero bytes shipped).
  • RTL/bidi first-classisRtl / direction set <html dir>; bidiIsolate wraps embedded text.
  • Locale routingparseLocalePath / localizePath / stripLocale.
  • FormattingformatNumber / formatCurrency / formatDate / formatRelativeTime / formatList.
  • Font-subsetting is automatic — because messages render to HTML in the active locale, the per-route subsetter ships exactly that locale's glyphs, with no configuration.

The client switch lives at @gomani/i18n/client (setLocale writes the cookie and reloads, so the next render is fully server-decided).