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

@dokebi/i18n

v0.2.8

Published

Compiled translation catalogs, locale negotiation, cardinal plurals and named Intl formats.

Readme

@dokebi/i18n

Application-owned translations with immutable locale views, compiled named placeholders, cardinal plurals, language negotiation and reusable Intl number/date formats. Optional; no web dependency or automatic request hooks.

Install with npx dokebi add @dokebi/i18n in a Dokebi project. Edit src/infra/i18n/extension.ts; it starts with an English catalog. Configure options.dokebi-i18n.defaultLocale in private dokebi.yaml when changing the default.

See AI.md for the complete API, message syntax, limits and error handling. Node >=24.0.0 and core ^0.4.0 are required. This is a plain-text message format, not full ICU MessageFormat or a translation service.

Store translations by language and namespace, for example src/shared/locales/en/auth.json and ko/auth.json. The generated entry discovers these files with loadCatalogs from @dokebi/i18n/catalogs. Nested JSON keys resolve as auth.password.minimum. Use translator.t(key, defaultValue, parameters?) for an explicit fallback, or t(key, parameters?) for the configured locale fallback chain.

Optional HTTP integration

Set options.dokebi-i18n.http.enabled: true with web installed. Use request.i18n.t('auth.password.minimum', 'At least eight characters'); the plugin selects the language, attaches the immutable translator, supplies the page locale and manages language response headers. Application code does not need a shared/i18n/server.ts hook. The server provider remains usable without HTTP.

Vue pages

With HTTP integration on, every page also gets the prop i18n: the messages of its namespaces (http.pageMessages, default all; pageMessages(request, 'posts') adds one for a route), sent once per browser: Inertia visits name the bundles the page holds, and the browser keeps them between page loads (http.pageCache, a cookie of content hashes), so a reload's HTML leaves them out (D-0126). Inertia apps made by dokebi app add --inertia install the browser runtime of @dokebi/template-inertia/i18n in views/app.js and views/ssr.js; pages call useI18n() for t, n, d and switchLocale with the same rules as the server. See AI.md.

Catalogs are shared application resources at src/shared/locales/<language>/<namespace>.json. Use CLI 0.4.6 or newer. Existing legacy catalog folders and edited entries are preserved during upgrades; follow the migration instructions before removing them.