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

@eloqnt/cli

v0.6.33

Published

A linter for your translation files, with AI translation built in.

Readme

@eloqnt/cli

eloqnt/cli is a linter for your translation files. It catches errors before they ship, and optionally fills in missing translations.

Documentation · Configuration


Start by linting your project for common problems:

$ eloqnt lint

messages/es.json
│
│  "kFvGpR": "Tienes mensajes nuevos"
│            ─┬──────────────────────
│             ╰─ Missing ICU argument: {count} (inconsistent-args)
│
│  "X0ha1a": "Save changes"
│            ─┬────────────
│             ╰─ Missing translation in es.json (missing-translation)

✗ 1 error
! 1 warning

→ Run `eloqnt translate` to fill in 1 missing translation

Linting runs static analysis on your source code and matches it against your messages, catching issues like unused messages, missing translations, broken ICU arguments, and more.

Setup

1. Install the CLI

Add the CLI as a local project dependency:

npm install @eloqnt/cli --save-dev

If you're in a monorepo, install it within local packages as needed.

2. Add a config file

Create a config file at .eloqnt/config.ts:

import {defineConfig} from '@eloqnt/cli';

export default defineConfig({
  // The folder containing your source code
  // (optional, only if you use next-intl)
  srcPath: './src',

  // Where and how you store your messages
  messages: {
    path: './messages',
    locales: 'infer',
    sourceLocale: 'en',
    format: 'json'
  }
});

All paths are relative to your project root. For more sophisticated setups like monorepos or when not using next-intl, see the configuration docs.

3. Lint your source code and messages

npx eloqnt lint

See eloqnt lint for details.

Start translating

Once linting works, you can optionally use eloqnt translate to fill in any missing translations:

$ eloqnt translate

✔  Context enrichment complete
✔  Styleguides loaded (global, es)
✔  Translated de, es via eloqnt/engine (hosted)
✔  Post-translation checks done

messages/
  de.json  2 translated
  es.json  2 translated

✔ Project fully translated

Source strings are enriched with context from their call sites, styleguides steer tone and terminology, and post-translation checks retry anything that comes back wrong.

To get started with translating, log into eloqnt/engine first.