Beacon 1.1.2
Beacon 1.1.2 — the CLI is now @martin-k-m/beacon-cli
The @beacon scope is not available on npm (and the unscoped beacon / beacon-cli names are taken), so the published CLI moves to the maintainer's existing scope.
npm install -g @martin-k-m/beacon-cli
beacon analyze facebook/reactNotes
- The command is unchanged — still
beacon. Only the npm package name changed. - The package was never published under the old name, so there is nothing to migrate.
- Internal workspace packages (
@beacon/analytics,@beacon/shared, …) keep their names — they are not published. - The release workflow (turbo filters +
npm pack/npm publish) targets the new name.
No functional changes — the Phase 2 features shipped in v1.1.0.