@jsonpages/stack
v1.0.56
Published
JsonPages tenant stack manifest — single source of truth for dependency versions
Downloads
5,497
Readme
@jsonpages/stack
Single source of truth for JsonPages tenant dependency versions (enterprise stack manifest).
Purpose
- Core syncs its
peerDependenciesfrom this manifest (viaprepackscript). - CLI uses this manifest when projecting a new tenant so
npm installgets the exact versions defined here. - No version drift: one file to change when upgrading React, Vite, React Router, etc.
Workflow
- Upgrade stack: Edit
stack-versions.json(dependencies, devDependencies, peerDependencies). KeeppeerDependenciesin sync with what Core supports. - Publish order: Publish
@jsonpages/stackfirst, then@jsonpages/core, then@jsonpages/cli. - From repo: Run
npm installat monorepo root so workspace deps resolve; then build/publish Core and CLI as needed.
Consumers
| Package | Use |
|----------------|-----|
| @jsonpages/core | prepack runs scripts/sync-peers-from-stack.js → copies peerDependencies into Core’s package.json. |
| @jsonpages/cli | On jsonpages new tenant <name>, installs deps with name@version from dependencies and devDependencies. |
File layout
stack-versions.json— canonical versions (peerDependencies, dependencies, devDependencies).index.js— ESM export for Node (used by Core sync script and CLI).
