[pviti]

Clear Node.js error, cli:update stays on the current major

Users on Node.js 20 updated the 6.x CLI with cli:update and ran into two problems.

1. cli:update moved them to 7.0.0. The 6.x command runs npm install -g @commercelayer/cli, without a version and without checking Node.js. It then printed the version of the process still running, the previous one (6.9.3), so the update looked failed.
2. CLI 7 fails on Node.js 20. It stops while loading with ERR_REQUIRE_ESM and prints the minified source of cli-core. I reproduced it with CLI 7.0.0 on Node.js 20.5.1 (the official binary, checksum verified).

Changes

• bin/run.js checks engines.node before loading anything and says what to do instead:

  Commerce Layer CLI 7.0.0 requires Node.js >=22.13 (current: 20.5.1).
  Update Node.js, or install the previous CLI major, which supports older Node.js versions:
  
    npm install -g @commercelayer/cli@6
  

  The check is in src/engines.ts, with no imports, so it loads on any Node.js.
• cli:update works like the plugins (feat(cli): plugins stay on their major unless --latest is given #293).
  • By default it installs the latest version of the current major (@^7).
  • --latest installs a new major. It cannot be used together with --version.
  • A release whose engines.node doesn't match the Node.js in use is not installed: the command stops and names the Node.js version needed.
• After the update the command shows the version npm installed (npm ls -g), for example 6.9.3 -> 6.9.9 or "up to date". When a new major is available it says so: run cli:update --latest, or the release needs a newer Node.js.
• Update notice: for a new major it suggests cli:update --latest.

Verification

• Node.js 20.5.1: the branch CLI prints the message above and exits with code 1, instead of crashing.

• cli:update, with npm writing to an isolated prefix (npm_config_prefix), so no real global install was touched:

  Case	Output
  From 7.0.0	"is up to date: 7.0.0"
  From a simulated 6.9.3	"updated: 6.9.3 -> 6.9.9", then the 7.0.0 hint with --latest
  --latest --version 7.0.0	error, the flags are exclusive

• Tests: unit tests for the version check, the error message and the update target. CLI tests: 35 passing. The 2 that fail locally (applications:login, config:show) fail on main too and depend on the environment.

• pnpm lint passes and docs/cli.md is regenerated.

Not included

The 6.x CLI keeps its old cli:update, which moves to the latest major. Only a 6.x patch could change that, and those users would only get it with cli:update -v 6.

🤖 Generated with Claude Code

[pviti]

Merged into #295, a single PR to review with #293.