@lightnet/cli 4.1.0 → 4.2.0

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @lightnet/cli
 
+## 4.2.0
+
+### Minor Changes
+
+- [#423](https://github.com/LightNetDev/LightNet/pull/423) [`30fabef`](https://github.com/LightNetDev/LightNet/commit/30fabef4897506cf4d0194b8883257de513ec452) - Add a new `lightnet check-files` command to validate orphaned and missing content files and thumbnails in LightNet site projects.
+
+## 4.1.1
+
+### Patch Changes
+
+- [#404](https://github.com/LightNetDev/LightNet/pull/404) [`5acab49`](https://github.com/LightNetDev/LightNet/commit/5acab49ca79078edbba3868b9b7bce249b2fca8a) - Update dependencies.
+
 ## 4.1.0
 
 ### Minor Changes

package/README.md

@@ -1,64 +1,15 @@
-# `@lightnet/cli`
+# LightNet CLI
 
-Command-line tools for working with LightNet projects.
+Command-line tools for working with LightNet sites. The CLI currently includes translation validation and file consistency checks.
 
 ## Install
 
 ```bash
-npm install --save-dev @lightnet/cli
+pnpm add --D @lightnet/cli
 ```
 
-You can also run the CLI without adding it to your project first:
+## LightNet CLI reference
 
-```bash
-npx @lightnet/cli --help
-```
-
-## Usage
-
-The package exposes the `lightnet` binary:
-
-```bash
-lightnet <command> [options]
-```
-
-Get the full command list at any time with:
-
-```bash
-lightnet --help
-```
-
-## Commands
-
-### `check-translations`
-
-Checks the translation data produced by the latest LightNet build and reports
-missing locale values.
-
-```bash
-lightnet check-translations
-```
-
-> [!NOTE]
-> `check-translations` only validates translations that were actually used
-> during the last build. For example, it would not report a missing category
-> label translation if that category label was never referenced while building
-> the site.
-
-What it does:
-
-- Reads the cached translation build output from `node_modules/.cache/lightnet/`
-- Verifies every translation has values for every configured locale
-- Groups missing translations by source to make follow-up work clearer
-
-When to use it:
-
-- After building a LightNet site
-- In CI to catch incomplete translations before deploys
-- While adding new locales or updating translation maps
-
-Expected setup:
+See command-line tools reference documentation at:
 
-- Run your project build first so LightNet can generate its translation cache
-  If the cache is missing, the command will fail and prompt you to run a build
-  first.
+https://docs.lightnet.community/resources/lightnet-cli-reference/

package/package.json

@@ -3,7 +3,7 @@
   "description": "CLI for managing LightNet projects",
   "type": "module",
   "license": "MIT",
-  "version": "4.1.0",
+  "version": "4.2.0",
   "publishConfig": {
     "access": "public"
   },
@@ -25,7 +25,7 @@
     "CHANGELOG.md"
   ],
   "dependencies": {
-    "commander": "^14.0.3"
+    "commander": "^15.0.0"
   },
   "engines": {
     "node": ">=22"