@eonium/compass-be-sherpa
v0.5.0
Published
Backend-specific Sherpa generator for Eonium Compass projects.
Readme
@eonium/compass-be-sherpa
Backend-specific Sherpa generation for Eonium Compass projects.
Package boundary
@eonium/compass-be-sherpa owns deterministic backend project inspection and backend Sherpa file generation. It uses @eonium/compass-core for repo-safe file writes and @eonium/compass-sherpa for canonical Compass/Sherpa paths.
This package may inspect backend project facts such as package.json, TypeScript config, module kind, available scripts and likely source directories. It must not own DB engines, auth providers, HTTP runtime helpers, app schemas or business workflows.
Supported command
The CLI exposes this package through:
eonium sherpa init backend --dry-run
eonium sherpa init backend --yes
eonium sherpa init backend --yes --force
eonium sherpa init backend --dry-run --jsonWrite behaviour
--dry-runreports the files that would be created or updated and writes nothing.--yescreates missing backend Sherpa files.- Existing user-authored files are skipped by default.
--forcepermits existing generated targets to be updated when their content differs.- Every run reports created, updated, skipped, warnings and errors through the Compass change-report shape.
Validation guarantees
A successful write creates the canonical .eonium/compass/sherpa/ root entrypoint, required backend Sherpa files, a backend changelog index and a changelog area registry. The generated structure is intentionally minimal but should be valid for eonium sherpa validate.
