@ai-translate/cli 0.2.3 → 0.4.0

package/README.md

@@ -7,10 +7,10 @@ See the [project README](../../README.md) for what the toolkit does and how a sy
 ## Install
 
 ```bash
-npm install --save-dev @ai-translate/cli
+npx ai-translate init
 ```
 
-Requires Node 20.19 or newer.
+Automatic setup with the default provider requires Node 22 or newer. The CLI itself supports Node 20.19 or newer.
 
 ## Configuration
 
@@ -56,25 +56,46 @@ This is how a provider API key normally reaches your config, for example `apiKey
 
 ### `init`
 
-Detects the project's Next.js localization setup and writes `ai-translate.config.ts` for it. This is the only command that runs without an existing config.
+Detects the project's localization resources, writes its config, and installs the required dependencies using the project's npm, pnpm, Yarn, or Bun. Adds missing translation scripts, `.env.example`, and ignore entries for local secrets and `node_modules`. Swift-only projects get a private tooling manifest. This command runs without an existing config.
 
 ```bash
 ai-translate init
 ai-translate init --preview
 ai-translate init --integration i18next
+ai-translate init --locale fr --locale pl
+ai-translate init --no-install
+ai-translate init --package-manager pnpm
 ```
 
-Recognises **next-intl** and **i18next** (including `react-i18next` and `next-i18next`), inferring the message layout, the locale list, and the source locale, then printing the evidence behind each conclusion.
+Recognises **next-intl**, **i18next** (including Expo/React Native projects using `react-i18next`), **Expo native locale mappings**, and **Apple localization** (`.xcstrings` catalogs and `.lproj/*.strings` tables). Detection infers source and target languages from resources and Xcode settings and prints the evidence behind each conclusion. Independent setups with the same source language become one configuration, retaining each catalog's message format. Overlapping detections or conflicting source locales require an explicit `--integration` choice.
 
-It writes exactly one file and nothing else. Installing packages, setting `OPENAI_API_KEY`, and reviewing the model choice are printed as next steps rather than done for you, so running it against an unfamiliar repository is safe.
+For an Xcode or Apple Swift package project without resources, `init` writes a starter config with explicit extraction instructions. Create and populate a String Catalog with Xcode, then configure your target languages. `init` does not extract hardcoded Swift, JavaScript, or Rust text and never invents target languages. Expo and Tauri projects without localization resources must externalize their text first.
+
+Native configs use explicit file includes; an empty starter uses `include: []`.
+After creating or repairing resources, review `init --preview` and update the
+includes. Detection partitions mixed Base/source tables, reports neighboring
+projects with different source languages, and excludes generated native output.
+
+Custom detectors use the platform-neutral `@ai-translate/integrations` interfaces. Adapter plans declare the package, factory export, and literal options, so adding a platform does not require changing the CLI's config renderer. `@ai-translate/next` retains its existing detection APIs for compatibility.
+
+`--preview` shows the full plan without writes or network calls. `--no-install` creates setup files and prints the remaining install command. Installation disables lifecycle scripts. Required `@ai-translate/*` registry packages are refreshed to `@latest` so older adapters cannot silently ignore new config options. Existing runtime, development, and optional dependency categories are preserved. Unrelated dependency versions and scripts are preserved; custom workspace, file, link, Git, and alias sources are kept with a notice. Declared dependencies are installed even in a fresh clone. A failed install keeps setup files so the command can be retried. Identical configs can be resumed; replacing a changed config requires `--force`. All supported config extensions are protected.
+
+After installation, init loads the generated config and validates source resources without making translation requests. Missing target translations are expected at this stage.
+
+The CLI never invents credentials or target languages. Set the provider key in your shell or `.env.local`, and use repeated `--locale` options if languages cannot be inferred. It does not start paid translation calls during setup. Unknown package managers and ambiguous lockfiles require `--package-manager`; workspace package managers are inherited.
+
+Expo detection reads committed `expo.locales` mappings in `app.json` or a static exported `app.config.ts` / `.js` object. Computed config is not executed. Shared i18next UI and native metadata can be translated in the same configuration.
 
 | Flag | Effect |
 | --- | --- |
-| `--preview` | Print the config that would be written and touch nothing. |
+| `--preview` | Show the complete setup plan without writes or installation. |
 | `--integration <id>` | Choose between setups when a project matches more than one. |
-| `--force` | Overwrite an existing `ai-translate.config.ts`. Refuses without it. |
+| `--force` | Replace a changed existing config, preserving its filename. |
+| `--locale <locale>` | Set a target locale; repeat for multiple languages. |
+| `--package-manager <name>` | Select npm, pnpm, yarn, or bun explicitly. |
+| `--no-install` | Prepare setup files and print the dependency install command. |
 
-Exits non-zero when nothing is recognised, when a named integration was not detected, or when a config already exists and `--force` was not passed.
+Exits non-zero when nothing is recognised, when a named integration was not detected, when a changed config exists without `--force`, or when installation or source validation fails.
 
 ### `sync`
 
@@ -88,6 +109,10 @@ ai-translate sync --locale de --catalog messages
 
 Writes happen inside a staged transaction: files and state are committed together only if the run converges, so an interrupted or failing sync leaves your content untouched. When semantic audits reject a translation, the run retries it up to `validation.semanticRepairAttempts` times before failing.
 
+Before committing, the CLI verifies that live files still match the snapshots it
+staged. If a developer or Xcode saved a file during translation, the run aborts
+without replacing those edits. Rerun to translate from the updated resources.
+
 Exits non-zero if any entry failed, if audits did not converge, or if a `--dry-run` exceeded the configured `validation.dryRunBudget`.
 
 ### `check`

package/dist/bin.mjs

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { n as runCli } from "./src-Cnnq284f.mjs";
+import { n as runCli } from "./src-SwBEpdIU.mjs";
 //#region src/bin.ts
 const exitCode = await runCli();
 process.exit(exitCode);

package/dist/index.d.mts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.mts","names":[],"sources":["../src/config.ts","../src/index.ts"],"mappings":";;;wBA4BgB,eAAe,aAAa;wBAiBtB,aAAa,cAAc,QAAQ;wBA+BnC,WACpB,aACA,wBACC;EAAU,QAAQ;EAAmB;;;;wBCkflB,OACpB,0BACA,eACC"}
+{"version":3,"file":"index.d.mts","names":[],"sources":["../src/config.ts","../src/index.ts"],"mappings":";;;wBA4BgB,eAAe,aAAa;wBAiBtB,aAAa,cAAc,QAAQ;wBA+BnC,WACpB,aACA,wBACC;EAAU,QAAQ;EAAmB;;;;wBCqgBlB,OACpB,0BACA,eACC"}

package/dist/index.mjs

@@ -1,2 +1,2 @@
-import { a as loadEnvFiles, i as loadConfig, n as runCli, r as findConfigPath, t as defineConfig } from "./src-Cnnq284f.mjs";
+import { a as loadEnvFiles, i as loadConfig, n as runCli, r as findConfigPath, t as defineConfig } from "./src-SwBEpdIU.mjs";
 export { defineConfig, findConfigPath, loadConfig, loadEnvFiles, runCli };