chore: initial public release

Author: Starllordz

.github/workflows/publish.yml

@@ -0,0 +1,69 @@
+name: Publish to npm
+
+on:
+  push:
+    tags:
+      - 'v*.*.*'
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      id-token: write
+    
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '22.20.0'
+          registry-url: 'https://registry.npmjs.org'
+      
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 10.11.1
+      
+      - name: Get pnpm store directory
+        shell: bash
+        run: |
+          echo "STORE_PATH=$(pnpm store path --silent)" >> $GITHUB_ENV
+      
+      - name: Setup pnpm cache
+        uses: actions/cache@v4
+        with:
+          path: ${{ env.STORE_PATH }}
+          key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
+          restore-keys: |
+            ${{ runner.os }}-pnpm-store-
+      
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+      
+      - name: Run tests
+        run: pnpm run test
+      
+      - name: Build project
+        run: pnpm run build
+
+      - name: Validate version matches tag
+        run: |
+          PACKAGE_VERSION=$(node -p "require('./package.json').version")
+          TAG_VERSION=${GITHUB_REF_NAME#v}
+          
+          echo "Package version: $PACKAGE_VERSION"
+          echo "Tag version:     $TAG_VERSION"
+          
+          if [ "$PACKAGE_VERSION" != "$TAG_VERSION" ]; then
+            echo "Error: package.json version ($PACKAGE_VERSION) does not match git tag version ($TAG_VERSION)."
+            exit 1
+          fi
+      
+      - name: Publish to npm
+        run: pnpm publish --access public --no-git-checks
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+

.gitignore

@@ -0,0 +1,27 @@
+# Environment variables
+.env
+
+# Build
+build/
+
+# Node modules
+node_modules/
+
+# OS files
+.DS_Store
+
+# Lara 
+lara.yaml
+.lara/
+
+# Test files
+i18n-test/
+
+# VSCode files
+.vscode/
+
+# Coverage files
+coverage/
+
+# tmp files
+tmp/

.prettierignore

@@ -0,0 +1,5 @@
+node_modules
+build
+dist
+*.map
+pnpm-lock.yaml

.prettierrc.json

@@ -0,0 +1,11 @@
+{
+  "semi": true,
+  "trailingComma": "es5",
+  "singleQuote": true,
+  "printWidth": 100,
+  "tabWidth": 2,
+  "useTabs": false,
+  "arrowParens": "always",
+  "endOfLine": "lf",
+  "bracketSpacing": true
+}

README.md

@@ -0,0 +1,239 @@
+<div align="center">
+
+# 🚀 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](docs/config/formats.md) for details.
+
+[![Version](https://img.shields.io/badge/version-1.0.0-blue.svg)](https://github.com/translated/lara-cli)
+
+</div>
+
+## 📑 Table of Contents
+
+- [Installation](#installation)
+- [Setting Up Your Project](#setting-up-your-project)
+- [Local Development Setup](#local-development-setup)
+- [Technology Stack](#technology-stack)
+- [Supported Locales](#supported-locales)
+- [Documentation](#documentation)
+
+## Installation
+
+### Requirements
+
+- Node.js v18 or higher
+
+### Install via npm
+
+The easiest way to get started is to install Lara CLI globally via npm:
+
+```bash
+npm install -g @translated/lara-cli
+```
+
+Once installed, you can use it from any directory:
+
+```bash
+# 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](https://support.laratranslate.com/en/api-key-for-laras-api).
+
+```bash
+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:
+
+```bash
+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](https://support.laratranslate.com/en/how-glossaries-work-in-lara).
+
+### Translate Your Files
+
+To translate your files into the target locales, run:
+
+```bash
+lara-cli translate
+```
+
+That's it – you're ready to go!
+
+> **📖 Documentation:** For detailed information about commands, see [Init Command](docs/commands/init.md) and [Translate Command](docs/commands/translate.md).
+
+## 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**
+
+```bash
+git clone https://github.com/translated/lara-cli.git
+```
+
+2. **Navigate to the cloned repository**
+
+```bash
+cd lara-cli
+```
+
+3. **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.
+
+```bash
+pnpm install
+pnpm run build
+```
+
+4. **Setup pnpm global bin directory (first time only)**
+
+```bash
+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:
+
+```bash
+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.
+
+5. **Link globally**
+
+```bash
+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:
+
+```bash
+/Users/username/Library/pnpm/global/5:
++ lara-cli version <- ../../../../Projects/translated/lara-cli
+```
+
+6. **Development Complete - Use anywhere**
+
+Now that Lara CLI is linked globally, you can use it from any directory on your system:
+
+```bash
+# 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](docs/config/locales.md#supported-locales).
+
+## Documentation
+
+For detailed documentation on using Lara CLI:
+
+### Commands
+
+- [Init Command](docs/commands/init.md) - Initialize your project
+- [Translate Command](docs/commands/translate.md) - Translate your files
+- [Memory Command](docs/commands/memory.md) - List available Translation Memories
+- [Glossary Command](docs/commands/glossary.md) - List available Glossaries
+
+### Configuration
+
+- [Configuration Overview](docs/config/README.md) - Configuration system overview
+- [Supported Formats](docs/config/formats.md) - Supported file formats (JSON, PO, etc.)
+- [Locales Configuration](docs/config/locales.md) - Configure source and target languages
+- [Files Configuration](docs/config/files.md) - Configure file paths and patterns
+- [Instructions](docs/config/instructions.md) - Configure translation instructions
+- [Translation Memories](docs/config/memories.md) - Configure Translation Memories
+- [Glossaries](docs/config/glossaries.md) - Configure Glossaries
+
+### Format-Specific Guides
+
+- [TS Files Guide](docs/config/files/ts-files.md) - Complete guide for TypeScript files
+- [PO Files Guide](docs/config/files/po-files.md) - Complete guide for gettext PO files
+- [Vue Files Guide](docs/config/files/vue-files.md) - Complete guide for Vue I18n single-file components
+- [Markdown Files Guide](docs/config/files/md-files.md) - Complete guide for Markdown and MDX files
+- [Android XML Files Guide](docs/config/files/android-xml-files.md) - Complete guide for Android XML string resource files