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

@i18nai/cli

v0.0.1-dev.0.0.12

Published

> [!WARNING] > This library is currently in development and not all features are available.

Readme

@i18nai/cli

[!WARNING]
This library is currently in development and not all features are available.

Command-line interface for managing internationalization in your projects using the i18n.ai platform.

Installation

# Global installation (recommended)
npm install -g @i18nai/cli

# Local installation
npm install --save-dev @i18nai/cli

Features

  • 🚀 Quick project initialization
  • 🔄 Automated translation generation
  • 📁 Structured locale file management
  • 🔑 Integration with i18n.ai API
  • 🎯 Support for nested translation keys
  • 🔒 Preserves existing translations
  • ⚡️ Fast and efficient processing

Commands

Initialize Project

Sets up the i18n configuration and creates initial locale files in your project.

i18nai init

This command will:

  1. Create an i18n directory in your project root
  2. Generate a config.json file with default settings
  3. Create locale files for English, Spanish, and French
  4. Set up sample translations to get you started

Generated project structure:

your-project/
└── i18n/
    ├── config.json
    └── locales/
        ├── en.json
        ├── es.json
        └── fr.json

Default configuration (config.json):

{
  "name": "your-app-name",
  "defaultLang": "en",
  "supportedLangs": ["en", "es", "fr"]
}

Translate Content

Automatically translates your content to all supported languages using the i18n.ai API.

# Basic usage
i18nai translate

# Using a custom API host
i18nai translate --host=http://localhost:3000
# or
i18nai translate -h=http://localhost:3000

This command:

  • Reads your English translations
  • Uses the i18n.ai API (or specified host) to translate to configured languages
  • Updates locale files with new translations
  • Preserves existing translations
  • Handles nested translation structures

Options

| Option | Alias | Description | Default | |--------|-------|-------------|---------| | --host | -h | API host URL | https://i18n.ai |

Configuration

Project Configuration

The i18n/config.json file supports the following options:

{
  "name": "your-app-name",     // Project name
  "defaultLang": "en",         // Source language
  "supportedLangs": [          // Target languages
    "en",
    "es",
    "fr"
  ]
}

API Configuration

To use the translation features:

  1. Sign up at i18n.ai
  2. Get your API key from the dashboard
  3. Set up your API key:
    export I18NAI_API_KEY=your_api_key

Translation File Format

Each locale file (locales/*.json) follows this structure:

{
  "simple": "Simple translation",
  "nested": {
    "key": "Nested translation",
    "with_params": "Hello, {{name}}!"
  },
  "deeply.nested.key": "Deeply nested translation"
}

Usage with CI/CD

For automated translation in CI/CD pipelines:

# Set API key in CI environment
export I18NAI_API_KEY=your_api_key

# Run translation
i18nai translate

Error Handling

The CLI provides clear error messages for common issues:

  • Missing API key
  • Invalid configuration
  • Network errors
  • Invalid translation files

Example error handling:

# Check if API key is set
if [ -z "$I18NAI_API_KEY" ]; then
  echo "Error: I18NAI_API_KEY is not set"
  exit 1
fi

# Run translation with error handling
i18nai translate || {
  echo "Translation failed"
  exit 1
}

Dependencies

  • Node.js >= 14
  • @i18nai/sdk: Core SDK package
  • Internet connection for translation features

License

MIT