formatjs_cli
A high-performance Rust-based command-line interface for FormatJS internationalization tools.
Overview
formatjs_cli is a high-performance Rust implementation of core FormatJS CLI workflows, providing fast tools for working with ICU MessageFormat messages in your internationalization workflow.
Why Use the Native CLI?
The native Rust CLI offers significant advantages over the Node.js-based @formatjs/cli:
- Faster Performance: 20.90x faster in the checked-in extraction benchmark, with parallel parsing for large compile and verify workloads
- Zero Node.js Runtime Dependency: Single binary with no Node.js runtime required for supported features
- Lower Memory Usage: Minimal memory footprint compared to Node.js
- Instant Startup: No Node.js initialization overhead
- Easy Distribution: Standalone binaries for CI/CD pipelines
- CI/CD Friendly: Fast, reliable, and cache-friendly
Benchmark results (processing 1,000 generated files with 9,406 messages):
- Pure TypeScript Node.js CLI: ~8.5 seconds
- Hybrid Node.js/native CLI: 744.86 ms, 12,628 messages/second
- Rust CLI: 35.65 ms, 263,876 messages/second
- Speedup vs hybrid CLI: 20.90x
Catalog benchmark results (20,000 generated messages, Apple Silicon, 2026-05-25; includes process startup and JSON I/O):
| Workflow | Before | After | Improvement |
|---|---|---|---|
compile --ast |
180.9 ms | 121.1 ms | 33.1% lower latency |
verify --structural-equality |
373.3 ms | 228.8 ms | 38.7% lower latency |
The native CLI aims to match @formatjs/cli for supported workflows. Some Node-specific behavior is intentionally not available in the standalone Rust binary, including loading arbitrary JavaScript formatter files with --format.
Threading
The native CLI parallelizes per-file and per-message work with Rayon. Extraction
uses per-file parallelism, while AST compilation and structural verification can
also parse individual messages in parallel. By default, Rayon uses the number of
available logical CPU cores. Set RAYON_NUM_THREADS to cap worker threads in
CPU-constrained environments:
RAYON_NUM_THREADS=4
Features
- Extract: Extract messages from JavaScript and TypeScript source files
- Compile: Compile messages for production use with optional minification
- Verify: Validate message files and check for missing/extra keys
- Compile-Folder: Batch compile all translation files in a folder
Quick Start
# Install from Cargo
# Extract messages from your source code
# Compile translations for production
# Verify translations are complete
Installation
Cargo
Install the published crate with Cargo:
Cargo installs the command as formatjs in ~/.cargo/bin:
If formatjs is not found, add Cargo's bin directory to your PATH:
For local development from this repository:
You can also run without installing:
Pre-Built Binaries
Download pre-built native binaries from the GitHub Releases page.
Available binaries:
formatjs_cli-darwin-arm64- macOS Apple Siliconformatjs_cli-linux-arm64- Linux ARM64formatjs_cli-linux-x64- Linux x86_64formatjs_cli-win32-x64.exe- Windows x64
Installation steps:
-
Download the appropriate binary for your platform:
# macOS Apple Silicon # Linux x86_64 # Linux ARM64 # Windows x64 -
On macOS or Linux, make it executable:
-
On macOS or Linux, optionally move it to your PATH:
-
Verify installation:
Using Bazel
Build the CLI using Bazel for host platform:
Run directly with Bazel:
Cross-Platform Release Builds
Build the release binaries for Darwin ARM64, Linux x64, Linux ARM64, and Windows x64:
Use bazel cquery --output=files <target> to locate each binary:
Local Cargo Build
Build and install from the local checkout using Cargo:
The built binary is target/release/formatjs.
Usage
Extract Command
Extract string messages from React components that use react-intl:
Full example with options:
Options:
[FILES]...- File glob patterns to extract from (e.g.,src/**/*.tsx)--format <FORMATTER>- Built-in formatter controlling JSON output shape (default,simple,transifex,smartling,lokalise, orcrowdin)--in-file <PATH>- File containing list of files to extract (one per line)--out-file <PATH>- Target file for aggregated .json output--id-interpolation-pattern <PATTERN>- Pattern to auto-generate message IDs (default:[sha512:contenthash:base64:6])--extract-source-location- Extract metadata about message location in source--additional-component-names <NAMES>- Additional component names to extract from (comma-separated)--additional-function-names <NAMES>- Additional function names to extract from (comma-separated)--ignore <PATTERNS>- Glob patterns to exclude--throws- Throw exception when failing to process any file--pragma <PRAGMA>- Parse custom pragma for file metadata (e.g.,@intl-meta)--preserve-whitespace- Preserve whitespace and newlines--flatten- Hoist selectors and flatten sentences
Compile Command
Compile extracted translation files into react-intl consumable JSON:
Full example with options:
Options:
[TRANSLATION_FILES]...- Glob patterns for translation files (e.g.,foo/**/en.json)--format <FORMATTER>- Built-in formatter that converts input toRecord<string, string>(default,simple,transifex,smartling,lokalise, orcrowdin)--out-file <PATH>- Output file path (prints to stdout if not provided)--ast- Compile to AST instead of strings--skip-errors- Continue compiling after errors (excludes keys with errors)--pseudo-locale <LOCALE>- Generate pseudo-locale AST output; requires--ast- Values:
xx-LS,xx-AC,xx-HA,en-XA,en-XB
- Values:
--ignore-tag- Treat HTML/XML tags as string literals
Compile-Folder Command
Batch compile all translation JSON files in a folder:
Full example with options:
Options:
<FOLDER>- Source directory containing translation JSON files<OUT_FOLDER>- Output directory for compiled files--format <FORMATTER>- Built-in formatter (default,simple,transifex,smartling,lokalise, orcrowdin)--ast- Compile to AST
Verify Command
Run checks on translation files to validate correctness:
Full example with all checks:
Options:
[TRANSLATION_FILES]...- Glob patterns for translation files--source-locale <LOCALE>- Required for checks to work (e.g.,en)--ignore <PATTERNS>- Glob patterns to ignore--missing-keys- Check for missing keys in target locales--extra-keys- Check for extra keys not in source locale--structural-equality- Check structural equality of messages
Compatibility Notes
formatjs_cli is intended to match @formatjs/cli where the Rust implementation supports the same feature. Known differences include:
--formataccepts built-in formatter names only. The Node.js CLI can also load custom JavaScript formatter files.- Extraction currently targets JavaScript and TypeScript source files. Framework template extraction for Vue, Svelte, Handlebars, Glimmer, GTS, and GJS is handled by the Node.js CLI.
Development
Running Tests
Using Bazel:
Using Cargo:
Project Structure
crates/formatjs_cli/
├── Cargo.toml # Cargo package manifest
├── BUILD.bazel # Bazel build configuration
├── README.md # This file
└── src/
└── main.rs # Main CLI implementation
Dependencies
clap: Command-line argument parsinganyhow: Error handlingserde&serde_json: JSON serializationformatjs_icu_messageformat_parser: ICU MessageFormat parsingformatjs_icu_skeleton_parser: ICU skeleton parsing
Performance
This Rust implementation provides significant performance improvements over the Node.js-based CLI, especially for:
- Large codebases: 10-100x faster extraction and compilation
- Batch processing: Parallel file and message processing for large catalogs
- CI/CD pipelines: Faster builds and deployments
- Memory efficiency: Lower memory usage for large message catalogs
See the benchmarks for detailed performance comparisons.
Contributing
Contributions are welcome! Please see the main FormatJS repository for contribution guidelines.
License
MIT
Related Packages
- @formatjs/cli - Node.js-based CLI
- formatjs_icu_messageformat_parser - ICU MessageFormat parser
- formatjs_icu_skeleton_parser - ICU skeleton parser