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

@translated/lara-cli

v1.1.1

Published

CLI tool for automated i18n file translation using Lara Translate

Downloads

1,126

Readme

🚀 Lara Cli – A Powerful CLI Tool for Instant i18n Localization

Lara Cli automates translation of your i18n files with a single command, preserving structure and formatting while integrating with a professional translation API. Given a source language, it translates your content to selected target languages based on your source i18n files.

Supports multiple file formats including JSON, PO (gettext), TypeScript, Vue I18n single-file components, Markdown and MDX files, and Android XML string resource files. See Supported Formats for details.

Version

📑 Table of Contents

Installation

Requirements

  • Node.js v18 or higher

Install via npm

The easiest way to get started is to install Lara CLI globally via npm:

npm install -g @translated/lara-cli

Once installed, you can use it from any directory:

# Get help with available commands
lara-cli --help

# Initialize a new Lara project
lara-cli init --help

# Translate your localization files
lara-cli translate --help

Setting Up Your Project

Add Your Credentials to .env

Create a .env file (or add the following lines to an existing .env) in the project where you want to run translations.

💡 Tip: If you don't have API keys yet, visit Lara's API key documentation.

LARA_ACCESS_KEY_ID=<YOUR_ACCESS_KEY_ID>
LARA_ACCESS_KEY_SECRET=<YOUR_ACCESS_KEY_SECRET>

Replace the placeholders with your actual credentials.

🔑 Need to update credentials? If your API keys expire or need updating, run lara-cli init --reset-credentials to safely update them in your .env file.

Initialize Your Project

In your project directory, run:

lara-cli init

This will start the interactive initialization process.

The CLI will automatically detect your localization directories and target locales from your existing project files, then guide you through a few questions. These will be used to generate the configuration file: lara.yaml.

Key features:

  • 🔍 Auto-detection: Scans your project for existing locale files and automatically suggests target locales
  • 📊 Smart display: For enterprise projects with many locales, uses formatted tables for better readability
  • ⚙️ Flexible configuration: Choose detected locales or manually add/remove as needed
  • 🎯 Project instructions: Optionally provide instructions to improve translation quality (e.g., tone, style, terminology)

Providing project instructions (optional but recommended):

During initialization, you can provide instructions to help improve translation quality. Instructions guide the translation service on tone, style, and terminology. This is especially useful for:

  • Tone requirements (formal, casual, professional, friendly)
  • Domain-specific terminology (medical, legal, technical, etc.)
  • Style preferences (concise, creative, detailed)

Providing glossaries (optional but recommended):

Lara's glossary system lets you define exactly how specific terms should be translated, across any text or document. Whether you work with technical terms, product names, or recurring brand phrases, glossaries are your best tool to ensure consistency and precision.

💡 Tip: For more information about glossaries, visit Lara's Glossary documentation.

Translate Your Files

To translate your files into the target locales, run:

lara-cli translate

That's it – you're ready to go!

📖 Documentation: For detailed information about commands, see Init Command and Translate Command.

Local Development Setup

If you want to contribute to Lara CLI or run it from source, follow these steps.

Requirements

  • Node.js v18 or higher
  • pnpm v8 or higher
  1. Clone the repository
git clone https://github.com/translated/lara-cli.git
  1. Navigate to the cloned repository
cd lara-cli
  1. Install dependencies and build

Note: This project uses pnpm. If you don't have it installed, run: npm install -g pnpm. Verify the installation with pnpm -v before proceeding with the following commands.

pnpm install
pnpm run build
  1. Setup pnpm global bin directory (first time only)
pnpm setup

This command configures your shell to add the pnpm global bin directory to your PATH. After running it, you'll see output similar to:

Appended new lines to /Users/<username>/.zshrc

Next configuration changes were made:
export PNPM_HOME="/Users/<username>/Library/pnpm"
case ":$PATH:" in
  *":$PNPM_HOME:"*) ;;
  *) export PATH="$PNPM_HOME:$PATH" ;;
esac

Add these lines to your shell profile (.zshrc, .bashrc, etc.) or restart your terminal to apply the changes. This ensures you can run globally installed pnpm packages.

  1. Link globally
pnpm link --global

Note: If you experience an error like ERR_PNPM_NO_GLOBAL_BIN_DIR, you may need to manually copy and paste the lines added by pnpm setup into your shell profile. After doing so, restart your terminal or source your profile file, and you should be able to proceed.

After running this command, the project will be successfully linked to the pnpm global library. You should see a response similar to:

/Users/username/Library/pnpm/global/5:
+ lara-cli version <- ../../../../Projects/translated/lara-cli
  1. Development Complete - Use anywhere

Now that Lara CLI is linked globally, you can use it from any directory on your system:

# Get help with available commands
lara-cli --help

# Initialize a new Lara project
lara-cli init --help

# Translate your localization files
lara-cli translate --help

Note: After making changes to the source code, run pnpm run build to update the global command.

Technology Stack

Lara CLI is built with modern technologies to ensure reliability, performance, and maintainability:

  • TypeScript - For type safety and developer experience
  • Commander.js - For CLI argument parsing and command structure
  • Zod - For robust schema validation
  • Inquirer.js - For interactive command-line user interfaces
  • Lara Translation API - For high-quality, context-aware translations

The codebase follows a modular architecture with clear separation of concerns, making it easy to extend and maintain.

Supported Locales

Lara CLI supports translations using different locale codes, following two main standards:

See the full list of supported locales.

Documentation

For detailed documentation on using Lara CLI:

Commands

Configuration

Format-Specific Guides