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

@the-lukez/li18n

v0.5.1

Published

<!-- The ?<num> is added because of caching. Caching time is very long it seems. -->

Readme

li18n

License Open Issues Closed Issues

A simple, type-safe i18n library for TypeScript. Define your messages in JSON, get fully-typed TypeScript functions out. No runtime parsing, no stringly-typed keys.

Full documentation at li18n.thelukez.com

[!IMPORTANT] This is a beta project. As of now, it should work but don't be surprised if you encounter bugs or rough edges. Feedback and contributions are very welcome!

Features

  • Fully typed — every message key becomes a typed TypeScript function; variables and conditionals are reflected in the signature
  • Conditionals & pluralization — boolean, string, and number conditionals with case-based dispatch
  • Async-safe locale scoping — built-in AsyncLocalStorage support via withLocale() for per-request isolation

Quick start

bun add -D @the-lukez/li18n
# or: npm install -D @the-lukez/li18n
// li18n.config.json
{
  "$schema": "./node_modules/@the-lukez/li18n/li18n.schema.json",
  "locales": ["en", "de"],
  "defaultLocale": "en",
  "messagesDir": "./messages",
  "outputDir": "./src/i18n"
}
// messages/en.json
{
  "greeting": "Hello {name}!",
  "itemCount": [
    {
      "var": { "num": "count" },
      "cases": {
        "=== 1": "1 item",
        "else": "{count} items"
      }
    }
  ]
}
li18n build
import { m, withLocale } from "./src/i18n";

const handler = withLocale(
  async (interaction) => {
    interaction.reply(m.greeting({ name: interaction.user.username }));
  },
  (interaction) => interaction.locale,
);

Or pass the locale directly to any message function:

m.greeting({ name: "Alice" }, "de"); // → "Hallo Alice!"
m.itemCount({ count: 1 }, "de"); // → "1 Element"
m.itemCount({ count: 5 }, "de"); // → "5 Elemente"

See the docs for the full message format, CLI reference, and runtime API.

License

MIT