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

@brandup/ui-i18n

v2.0.16

Published

Lightweight type-safe localization for web applications.

Readme

brandup-ui-i18n

Build Status

Lightweight type-safe localization for web applications.

The engine is generic: it does not know the concrete set of languages, the application passes it to createI18n. Keys are extracted from the lambda source (m => m.a.b.c), which gives autocomplete and refactoring safety. With resolveJsonModule TypeScript checks every dictionary against the model interface, so a missing key is caught at build time.

Installation

Install NPM package @brandup/ui-i18n.

npm i @brandup/ui-i18n@latest

Usage

import { createI18n } from "@brandup/ui-i18n";

export type ApplicationLanguage = "en" | "ru" | "ar" | "zh";

const i18n = createI18n<ApplicationLanguage>({
    lang: document.documentElement.lang, // raw value; region "ar-SA" is reduced to "ar"
    supported: ["en", "ru", "ar", "zh"],
    default: "en",
    rtl: ["ar"],
});

export const { CURRENT_LANG, IS_RTL, buildLocalization } = i18n;

Register a namespace with lazy dictionary loading (only the current and the default language are loaded):

interface CommonLocaleModel {
    layout: { footer: { copy: string } };
}

const localize = await buildLocalization<CommonLocaleModel>(
    "common", builder => builder
        .add("en", () => import("./en.json"))
        .add("ru", () => import("./ru.json"))
);

localize.t(m => m.layout.footer.copy, { year: "2025" });
localize.t("layout.footer.copy"); // safe string path

Behaviour

  • Fallback: current language, then default language, then the key path itself (shown in the UI instead of crashing).
  • RTL: IS_RTL for client-side logic; the dir attribute on <html> is set by the server.
  • Namespaces: a name can be registered once; a repeated buildLocalization for the same name is rejected, including while the first one is still loading. A build that failed is not cached, so it can be retried.
  • Testability: lang is accepted as a string, no DOM is required.
  • Lambda keys: arrow and transpiled function forms are supported, including block bodies. If a minifier ever breaks the parsing, use the string form t("a.b").

Depends on @brandup/ui-helpers (ObjectHelper.getProperty, formatText).