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

@stringlane/cli

v0.9.1

Published

Localization checks for your terminal and CI: ARB, iOS .strings/.stringsdict/.xcstrings, Android XML, i18next JSON.

Readme


Localization checks for your terminal and CI. Point it at a project folder; it tells you what is missing, what is broken, and sets an exit code CI can branch on.

Nothing writes without asking you first. inspect, check, plan and validate are read-only, and that is enforced rather than promised: a test suite snapshots every file's contents, size and modification time before and after each command and fails if anything moved. The commands that do write (init, apply, update, describe, add-locale, add-key, accept, pluralize, context --from, baseline write) each ask for confirmation, and refuse outright when there is no terminal to ask unless you pass --yes. A run that cannot ask does not guess.

Supports ARB (Flutter), iOS .strings / .stringsdict / .xcstrings, Android XML, and i18next JSON.

Install

npm i -g @stringlane/cli

Or run it without installing:

npx @stringlane/cli check .

The binary is stringlane. One bundled file, no runtime dependencies, Node 22 or newer. The tarball carries dist/stringlane.js, LICENSE, THIRD-PARTY-NOTICES.md and package.json. There is no sourcemap, deliberately.

Commands

stringlane <command> [project] [flags]

[project] defaults to the current directory.

Reading your project

| Command | What it does | Writes? | |---|---|---| | inspect | Reports what the project holds and what is missing | no | | check | Validates and sets an exit code for CI | no | | scan | Finds keys your code no longer calls, and keys it calls that do not exist. --ignore-key-pattern / --ignore-file (repeatable) silence a family; stringlane.yaml's ignoreKeyPatterns / ignoreFilePatterns make it permanent, and the flags add to that list | no | | plan | Lists what needs translating, for an agent to work from | no | | validate | Checks an agent's translations without touching your files | no |

Changing your project: every one of these asks first, or refuses without a terminal unless you pass --yes.

| Command | What it does | |---|---| | init | Detects the project and writes stringlane.yaml. For a new config on a project that loads cleanly it also turns source stamps on and writes .stringlane/source-stamps.json holding today's stamps. Commit both | | apply | Writes an agent's translations into your locale files | | update | Translates the missing strings with your own AI provider, then writes them | | describe | Writes key descriptions, so translations are made with context | | add-locale | Creates the file for a locale the project does not have yet | | add-key | Adds a new key with its base-language value to the base locale file | | accept | Marks translations as current against today's base text, in .stringlane/source-stamps.json | | pluralize | Replaces a key's single string with the plural forms your base language needs, in the base file only. Fixes a count_without_plural finding; --json without --yes previews and writes nothing | | context | Shows the product and terminology context; writes it with --from | | baseline write | Records today's issues (not stale or unconfirmed translations) so CI can start clean |

For AI agents

| Command | What it does | |---|---| | mcp | Serves this project to an agent over MCP (stdio) | | setup mcp | Shows your agent's MCP config, or writes it with --apply | | setup hooks | Shows the write guard for your agent's settings, or writes it with --apply | | hook | Answers an agent host's pre-write hook (reads stdin; not run by hand) |

Settings

| Command | What it does | |---|---| | telemetry status\|on\|off | Shows or changes whether usage data is sent |

stringlane --help lists every flag, and stringlane <command> --help lists the ones a single command takes.

Flags

The ones worth knowing before you read --help:

| Flag | Commands | Meaning | |---|---|---| | --json | inspect, check, plan, … | Emit the raw result envelope instead of human text | | --output <file> | report commands | Write the report to a file rather than stdout | | --fail-on <codes> | check | Only these issue codes set exit 1 (comma-separated) | | --target <locales> | plan | Only plan these locales (comma-separated) | | --yes | every writing command | Skip the confirmation prompt | | --force | init, setup mcp | Overwrite what is already there | | --apply | setup mcp, setup hooks | Write the change instead of printing it | | --provider, --model | update | AI provider and model; default to $STRINGLANE_AI_PROVIDER / $STRINGLANE_AI_MODEL | | --help, --version | all | Show help; print the version |

--fail-on decides which findings the exit code is computed from, in both directions: naming a code that is present exits 1 (including an informational finding that would not have failed on its own) and naming codes that are all absent exits 0. Nothing moves unless you ask twice, by passing the flag and naming the code; a run without --fail-on behaves exactly as it always has. A run that could not read your project still exits 2 no matter what you pass.

Bring your own key. update is the only command that talks to an AI provider, and it uses your key from your environment. StringLane never has one of its own, never writes yours anywhere, and never puts it in a plan, a report, or a log.

Exit codes

| Code | Meaning | |---|---| | 0 | No issues | | 1 | The project has localization issues | | 2 | The command could not run |

A broken gate and a failing gate are different things. 2 means stringlane never got far enough to have an opinion: a folder that is not a project, a config pointing outside the repository, a flag it does not recognise. A CI job that treats "non-zero" as "translations are missing" will report the wrong problem on the day it matters most.

In CI

- uses: actions/setup-node@v7
  with: { node-version: 22 }
- run: npm i -g @stringlane/cli
- run: stringlane check .

That is the whole integration. There is no packaged Action yet, deliberately, until there is evidence anyone wants one.

For a report your team can read on the PR:

stringlane check . --json --output stringlane-report.json

The JSON is the engine's own envelope, verbatim: protocolVersion, command, status, result, warnings, error. Switch on error.code, not on the message. The codes are stable and the prose is not.

Adopting on a project that is not clean

Most real projects fail check on day one, with hundreds of pre-existing issues. That is the point at which a gate normally gets switched off. Instead:

stringlane baseline write . --yes    # records today's issues
git add .stringlane/baseline.yaml
stringlane check .                   # now exits 0

From then on, check fails on issues that are new since the baseline. Recorded issues are reported as accepted rather than hidden, so the debt stays visible. When a recorded issue is fixed, its entry goes stale. It is reported, it still suppresses, and it clears the next time you run baseline write. Nothing expires on a timer: a gate that quietly starts failing because a date passed is a gate people turn off.

A baseline cannot hide a stale translation: baseline write leaves out translation_stale and translation_unconfirmed and says how many, and check exits 2 on a baseline that holds either. Run stringlane accept once you have checked the translations. A baseline written with stamps on by an earlier build needs stringlane baseline write again.

Telemetry

This tool sends usage data by default, tagged with a random install ID. It prints a notice saying so the first time you run it on a machine, before anything is sent.

What is sent. Every event carries the StringLane version, your operating system (macOS, Windows or Linux), whether it came from the CLI or the MCP server, and a random identifier generated on your machine. The identifier ties runs together so we can tell one person running ten commands from ten people running one. Counts and durations are sent as ranges, such as "11-50", never as exact numbers. There are four events:

  • Each command you run, including stringlane mcp: the command's name, how it ended (success, issues found, usage error, registry unreachable, or crash), how long it took, your project's format if the command opened one, and how many issues it found if it validated.
  • Each stringlane update that calls an AI model: whether you limited it to some locales with --target, whether the provider is a cloud service or a local model, how many strings it set out to translate, and whether the run finished, partly failed, failed or was cancelled.
  • The MCP server starting: nothing beyond what every event carries.
  • An MCP session ending: how long it lasted, how many tool calls it answered, and how many times each tool was called.

stringlane hook, the agent write guard, sends nothing. stringlane telemetry off sends the event for its own run, and nothing after it.

What is never sent: your translation keys or values, any text from your localization files, file paths, folder names, project names, the values of the arguments you passed (such as the locales you named), which AI provider or model you use, anything sent to or received from an AI provider including your API keys, error messages, and stack traces.

Turning it off. Any one of these is enough:

stringlane telemetry off        # persists on this machine
STRINGLANE_TELEMETRY=0          # one run, or export it
DO_NOT_TRACK=1                  # the cross-tool standard; honoured here

stringlane telemetry status shows the current state, the install ID (or none if this machine has not been given one), and whichever environment variable is deciding it. Nothing is sent from CI. A continuous-integration environment disables it outright, without asking. It is detected by any of CI, TF_BUILD (Azure Pipelines), BUILDKITE, TEAMCITY_VERSION, CODEBUILD_BUILD_ID, JENKINS_URL or bamboo_buildKey; on another runner, set DO_NOT_TRACK=1.

Data goes to our own service, which forwards it to Mixpanel's EU region under a one-way derived identifier and discards the network address it arrived from. Full detail: https://stringlane.app/privacy.

What it will not do

  • It will not write over a translation file. --output pointed at a file the project loaded is refused.
  • It will not follow a symlink out of your repository: not for --output, not for stringlane.yaml, not for the baseline. A repository that ships a redirect does not get to choose where a report lands.
  • It will not overwrite an existing stringlane.yaml without --force, and will not write anything at all without a terminal or --yes.
  • It holds no credential of ours and never writes one of yours. The environment variables it does read are listed under Telemetry above.