@ng-linguo/linguo 0.9.1 → 0.9.3

package/README.md

@@ -99,16 +99,34 @@ zero RxJS plumbing in your components.
 
 ## Install
 
+ng-linguo is two packages that do two different jobs at two different times — so
+you install both, once.
+
+**The runtime** — what your app imports and ships to the browser:
+
 ```bash
 npm i @ng-linguo/linguo @ngrx/signals
 ```
 
 Requires **Angular 18+**. `@ngrx/signals` is a peer dependency — bring your own.
 
+**The CLI** (`@ng-linguo/extract`) — the build-time tool that scans your source
+and produces the translation files the runtime loads. It's pure Node with zero
+Angular dependencies, so it installs as a dev dependency and never reaches the
+browser:
+
+```bash
+npm i -D @ng-linguo/extract
+```
+
+Its bin is `linguo-extract`; you run it with `npx linguo-extract …` (or from an
+npm script). Neither package depends on the other, so each stays minimal — the
+runtime renders translations in your app, the CLI generates them in your build.
+
 ## Getting started
 
 The fastest path from an empty Angular app to a translated one. Steps 1–3 get
-the runtime working; step 4 generates the real translation files.
+the runtime working; step 4 uses the CLI to generate the real translation files.
 
 ### 1. Configure the runtime
 
@@ -231,10 +249,11 @@ The strings above are also your source catalog. Use the
 JSON your loader serves:
 
 ```bash
-npx linguo-extract init --locales en,pl,de   # one-time: create linguo.config.json
-linguo-extract extract                        # scan source → en/pl/de .po catalogs
-linguo-extract translate --all                # fill missing entries with AI (optional)
-linguo-extract compile                        # .po → runtime JSON
+npm i -D @ng-linguo/extract                   # one-time: install the CLI
+npx linguo-extract init --locales en,pl,de    # create linguo.config.json
+npx linguo-extract extract                    # scan source → en/pl/de .po catalogs
+npx linguo-extract translate --all            # fill missing entries with AI (optional)
+npx linguo-extract compile                    # .po → runtime JSON
 ```
 
 That's the whole loop. See [Translation workflow](#translation-workflow) for the
@@ -275,13 +294,15 @@ they can render.
 `@ng-linguo/extract` is a pure-Node CLI (no Angular dependency, so it never
 drags the framework into your tooling) that turns your source into translation
 files and back. It reads a `linguo.config.json` — auto-discovered — listing your
-locales and paths.
+locales and paths. Install it once as a dev dependency; its bin is
+`linguo-extract`, so you invoke it with `npx` (or from an npm script):
 
 ```bash
-linguo-extract init       # create/edit linguo.config.json
-linguo-extract extract    # scan source → <locale>.po catalogs (additive)
-linguo-extract translate  # fill missing entries with AI (needs a translator)
-linguo-extract compile    # .po catalogs → runtime <locale>.json
+npm i -D @ng-linguo/extract   # install once; the bin is `linguo-extract`
+npx linguo-extract init       # create/edit linguo.config.json
+npx linguo-extract extract    # scan source → <locale>.po catalogs (additive)
+npx linguo-extract translate  # fill missing entries with AI (needs a translator)
+npx linguo-extract compile    # .po catalogs → runtime <locale>.json
 ```
 
 ### The interactive menu
@@ -314,11 +335,11 @@ their source text plus `context`. Re-running it is safe and idempotent.
 Adding a locale is a couple of steps — or a couple of clicks in the menu:
 
 ```bash
-linguo-extract init --locales en,pl,de,fr   # add `fr` to the config
-linguo-extract extract                        # seeds fr.po with the source strings
-linguo-extract translate --locale fr          # fill it in with AI…
-# …or: linguo-extract copyprompt fr           # …or copy a prompt for any chat model
-linguo-extract compile                        # produce fr.json
+npx linguo-extract init --locales en,pl,de,fr   # add `fr` to the config
+npx linguo-extract extract                       # seeds fr.po with the source strings
+npx linguo-extract translate --locale fr         # fill it in with AI…
+# …or: npx linguo-extract copyprompt fr          # …or copy a prompt for any chat model
+npx linguo-extract compile                       # produce fr.json
 ```
 
 ### Translating with AI
@@ -328,8 +349,8 @@ has all the context it needs. ng-linguo writes a self-contained prompt that
 teaches the model your `context` notes, slot tags, and plural rules, and only
 ever sends entries that are still missing. Two ways to run it:
 
-- **Clipboard (no key, no config):** `linguo-extract copyprompt pl` copies the
-  prompt; paste it into any chat model and save the reply over `pl.po`.
+- **Clipboard (no key, no config):** `npx linguo-extract copyprompt pl` copies
+  the prompt; paste it into any chat model and save the reply over `pl.po`.
 - **Automatic:** point the `translator` config field at a small module that
   calls your AI provider. ng-linguo builds the prompt and merges the reply; your
   SDK and API key stay yours. See the
@@ -342,12 +363,12 @@ Every command runs non-interactively and deterministically, so the pipeline
 drops into CI as-is:
 
 ```bash
-linguo-extract extract        # fails the build if it errors; idempotent otherwise
-linguo-extract translate --all  # optional: fill any gaps (needs a translator)
-linguo-extract compile
+npx linguo-extract extract          # fails the build if it errors; idempotent otherwise
+npx linguo-extract translate --all  # optional: fill any gaps (needs a translator)
+npx linguo-extract compile
 ```
 
-`init` is scriptable too: `linguo-extract init --locales en,pl,de --out public/i18n`.
+`init` is scriptable too: `npx linguo-extract init --locales en,pl,de --out public/i18n`.
 
 ## Configuration
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ng-linguo/linguo",
-  "version": "0.9.1",
+  "version": "0.9.3",
   "description": "A modern, signal-first i18n runtime for Angular 18+ — built on SignalStore, with a translator-safe slot syntax, ICU, and tree-shakeable HTTP loading.",
   "license": "MIT",
   "author": "jmwierzbicki",