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

@fieldlyab/translator-cli

v0.1.0

Published

Fieldly Translator developer CLI (ft) — push/pull/status translations between repos and Fieldly Translator.

Readme

ft — Fieldly Translator CLI

A thin command-line transport between your repo's translation files and Fieldly Translator (FT). It does not parse translation formats — it reads raw files at configured paths and POSTs/GETs them; FT's server-side engine handles every format (Rails YAML, ngx-translate/Transloco JSON, Android XML, iOS strings/stringsdict/xcstrings).

Cross-platform (macOS / Windows / Linux) via Node ≥ 18.

Install

npm install -g @fieldlyab/translator-cli

or run without installing:

npx @fieldlyab/translator-cli login

The binary is exposed as both ft and fieldly-translator.

Requirements

You need a Fieldly Translator account (sign in with Google or Microsoft SSO) and access to the project you're working on. Run ft from a repo that has a fieldly-translator.yml file at its root.

Commands

ft login   [--token [T]] [--host URL]              sign in via browser SSO, or paste a token
ft push    [--locales L] [--branch B] [--dry-run]  send new/changed source+authored keys up
ft pull    [--locales L] [--dry-run]               write FT-owned target locales into the repo
ft status  [--branch B] [--locales L]              report completeness; non-zero exit gates CI
ft get     KEY [--locale L]                         fetch a single key
ft request [--locales L] [--all]                    trigger translations for missing targets

Run ft <command> --help for the full option list.

Configuration

A single fieldly-translator.yml at the repo root declares the FT project, the locale roles (source / authored / target), and the translation file paths per platform and app.