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

@duckalization/translate

v0.1.0

Published

Agent-driven catalog translation: status diffing, work-order briefs, glossary/style enforcement, validated apply, and review metadata.

Readme

@duckalization/translate

Library for duckalization's translation workflow. It does not call a model and it does not invent copy. It diffs catalogs, writes a brief, validates the JSON an agent returns, merges it, prunes orphans, and records review metadata.

This is the library behind duckalize translate and duckalize review. Apps should depend on @duckalization/cli. Import this package when embedding the same checks in custom tooling.

The brief's embedded instructions are the contract; llms.txt section 7 is the same material in prose.

The loop

extract  →  source catalog + .meta.json
                ↓
status   →  which IDs are missing / orphaned in each target locale
brief    →  locales/.work/<locale>.brief.json   (work order, missing only)
                ↓
           agent translates the brief → <locale>.out.json
                ↓
apply    →  validate → merge into locales/<locale>.json
           + write locales/<locale>.review.json
check    →  CI gate (exit 1 if anything is still missing)
lint     →  apply-time checks on catalogs already on disk
prune    →  archive orphans to locales/.archive/, then drop them

review status / review approve read and write the sidecar; they do not translate. A brief includes source strings, call-site excerpts, the glossary subset, the style guide, and CLDR plural categories, so the agent does not need the repo. apply rejects the whole file on hard errors; nothing is written.

CLI

pnpm add -D @duckalization/cli
pnpm duckalize translate status
pnpm duckalize translate brief
pnpm duckalize translate apply locales/.work/es.out.json --by claude

Requires "targetLocales" in duckalization.config.json (or locales as CLI arguments). es.out.json is a convention; apply reads whatever path you pass.

Library API

pnpm add -D @duckalization/translate
import {
  resolveTranslateConfig,
  translationStatus,
  buildBrief,
  writeBrief,
  applyOutput,
  lintLocale,
  pruneLocale,
  reviewOverview,
  approve,
} from '@duckalization/translate';

const config = await resolveTranslateConfig({ cwd: process.cwd() });
const brief = await buildBrief(config, 'es');
await writeBrief(config, brief);
const result = await applyOutput(config, output, { by: 'claude' });
// result.applied === 0 if any diagnostic is an error; nothing was written

Complete usage guide: duckalization README.