@open-matrix/hive-pm (1.1.32)
Installation
@open-matrix:registry=npm install @open-matrix/hive-pm@1.1.32"@open-matrix/hive-pm": "1.1.32"About this package
hive-pm — what a package means
hive-pm creates, checks and publishes HiveCast packages: the layer of meaning
(the manifest, matrix.package.json) on top of npm's packages at rest.
Prior art: dotnet new plus NuGet; cargo new and cargo publish. npm stays
underneath and is never wrapped opaquely.
It is one of five tools, each owning one domain
(governing design §10.1):
hive-pm (packages), hivedock (running them), matrix (the bus), hivecast
(your account), npm (bytes).
Verbs
| Verb | Does | Prior art |
|---|---|---|
hive-pm new <service|application|component|cluster> <name> |
Scaffolds a package of that archetype. Inside a HiveCast source checkout it also joins the workspace (pnpm-workspace.yaml). An application gets Vite and browser.source, so hivedock up serves it with hot replacement |
dotnet new, cargo new |
hive-pm validate [target] |
Checks the manifest against matrix.package/v3 without contacting anything |
cargo check on the manifest |
hive-pm inspect [target] |
Prints what the package declares, offline | dotnet list package, npm view |
hive-pm publish [target] |
Validates, then npm publish |
dotnet nuget push, cargo publish |
hive-pm prove <manifest|package-install|application|credential-boundary> |
Runs the maintained conformance checks for a package | cargo test for platform conformance |
new options: --out <path>, --current-directory, --scope <npm scope>,
--description, --version, --yes, --git (creates and pushes the
repository in your Gitea namespace), --explain (prints the plan, writes
nothing), --json.
The development loop
hive-pm new application my-tool # scaffold; joins the workspace
pnpm install # links its dependencies
cd my-tool && hivedock up # it is in your Start menu; edits hot-replace
Inside a HiveCast source checkout, run the checkout's own tools with
pnpm exec (pnpm exec hive-pm new …, pnpm exec hivedock up): the
machine-wide commands are the installed release. A development environment
writes the checkout's .hivecast/deployment, so hivedock up needs no flags.
Not here
Running a package is hivedock; calling one is matrix invoke (or
hivecast invoke); signing in is hivecast login. The older matrix init,
element, actor-element, cqrs and webapp scaffolds duplicate hive-pm new
and are being deleted (design §15).
Dependencies
Dependencies
| ID | Version |
|---|---|
| @open-matrix/conformance-harness | 1.1.32 |
| @open-matrix/package-artifacts | 1.1.32 |
| commander | ^11.0.0 |
Development Dependencies
| ID | Version |
|---|---|
| @types/node | ^25.0.10 |
| esbuild | ^0.27.3 |
| tsx | ^4.15.6 |
| typescript | ^5.7.0 |