onemessagebus-cli 0.4.0

package/README.md

@@ -0,0 +1,17 @@
+# onemessagebus-cli
+
+The `onemessagebus` command, as a prebuilt binary.
+
+```bash
+npm install -g onemessagebus-cli
+onemessagebus --help
+```
+
+The binary ships inside a per-platform package that npm selects by `os`/`cpu`, so
+there is no compile step and no Rust toolchain to install. The same binary is on
+[PyPI](https://pypi.org/project/onemessagebus-cli/) (`pip install
+onemessagebus-cli`), and builds from source with `cargo install --git
+https://github.com/nickderobertis/onemessagebus onemessagebus-cli --locked`.
+
+See [the repository](https://github.com/nickderobertis/onemessagebus) for what it
+does and the contract it implements.

package/bin/onemessagebus.js

@@ -0,0 +1,90 @@
+#!/usr/bin/env node
+// Launcher for the `onemessagebus` command installed from the
+// `onemessagebus-cli` npm package.
+//
+// Like the PyPI wheels (maturin `bindings = "bin"`, see pyproject.toml), the npm
+// distribution carries the *prebuilt* Rust binary — no Rust toolchain, no
+// compile, no download at install time. The platform-specific binary ships
+// inside a per-platform package (`onemessagebus-cli-<platform>-<arch>`) the
+// published package lists in its `optionalDependencies`; npm installs only the
+// one whose `os`/`cpu` match the host, and this shim resolves it and execs it
+// with the caller's argv.
+//
+// This file is committed source; the version and the optionalDependencies are
+// written at publish time by scripts/npm-build.mjs, from Cargo.toml and its
+// TARGETS table, and that script also generates the per-platform packages from
+// the release binaries.
+
+const path = require("node:path");
+const { spawnSync } = require("node:child_process");
+
+// process.platform-process.arch -> the platform package that carries the binary.
+// The keys mirror the Rust target matrix in .github/workflows/release.yml and
+// the TARGETS table in scripts/npm-build.mjs, which generates the published
+// optionalDependencies; npm/test/platform-matrix.test.mjs holds them in lockstep.
+const PACKAGES = {
+  "linux-x64": "onemessagebus-cli-linux-x64",
+  "linux-arm64": "onemessagebus-cli-linux-arm64",
+  "darwin-x64": "onemessagebus-cli-darwin-x64",
+  "darwin-arm64": "onemessagebus-cli-darwin-arm64",
+  "win32-x64": "onemessagebus-cli-win32-x64",
+};
+
+// Every failure here is a failed install, so say what to do about it rather than
+// only what went wrong.
+const OTHER_INSTALLS =
+  "Install another way instead: 'pip install onemessagebus-cli', or " +
+  "'cargo install --git https://github.com/nickderobertis/onemessagebus onemessagebus-cli --locked'.";
+
+function fail(message) {
+  process.stderr.write(`onemessagebus: ${message}\n`);
+  process.exit(1);
+}
+
+function binaryPath() {
+  const key = `${process.platform}-${process.arch}`;
+  const pkg = PACKAGES[key];
+  // llmlint: ignore-block[changed_behavior_has_e2e] reaching this branch means running
+  // where no prebuilt package exists, and a test could only get there by lying to node
+  // about process.platform — which would prove the lie. The sibling branches are driven
+  // for real by npm/e2e/launcher.test.mjs, and npm's own os/cpu fields keep a user from
+  // installing a platform package this map does not name.
+  if (!pkg) {
+    fail(
+      `unsupported platform ${key}. Prebuilt binaries exist for: ` +
+        `${Object.keys(PACKAGES).join(", ")}. ${OTHER_INSTALLS}`,
+    );
+  }
+  // llmlint: ignore-end[changed_behavior_has_e2e]
+
+  const binName = process.platform === "win32" ? "onemessagebus.exe" : "onemessagebus";
+  try {
+    // Resolve the platform package's manifest, then locate the binary beside it.
+    // Resolving package.json (rather than the binary file directly) is portable
+    // across Node resolution modes and does not require an `exports` entry for a
+    // non-JS asset.
+    const manifest = require.resolve(`${pkg}/package.json`);
+    return path.join(path.dirname(manifest), "bin", binName);
+  } catch (_err) {
+    return fail(
+      `the platform package ${pkg} is not installed. This usually means npm ` +
+        "skipped optional dependencies (e.g. --no-optional / --omit=optional) " +
+        "or the install was for a different platform. Reinstall with optional " +
+        `dependencies enabled. ${OTHER_INSTALLS}`,
+    );
+  }
+}
+
+const result = spawnSync(binaryPath(), process.argv.slice(2), { stdio: "inherit" });
+
+if (result.error) {
+  fail(`failed to launch the onemessagebus binary: ${result.error.message}`);
+}
+
+// Re-raise a terminating signal so callers observe the true cause; otherwise
+// propagate the child's exit code verbatim — the contract assigns meaning to 1
+// and 2, and a caller reads them.
+if (result.signal) {
+  process.kill(process.pid, result.signal);
+}
+process.exit(result.status === null ? 1 : result.status);

package/package.json

@@ -0,0 +1,36 @@
+{
+  "name": "onemessagebus-cli",
+  "version": "0.4.0",
+  "description": "A typed NDJSON message bus: schema registry verbs and stream verbs over the agent profile.",
+  "keywords": [
+    "ndjson",
+    "events",
+    "message-bus",
+    "schema",
+    "cli"
+  ],
+  "homepage": "https://github.com/nickderobertis/onemessagebus",
+  "bugs": "https://github.com/nickderobertis/onemessagebus/issues",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/nickderobertis/onemessagebus.git"
+  },
+  "license": "MIT",
+  "author": "Nick DeRobertis",
+  "bin": {
+    "onemessagebus": "bin/onemessagebus.js"
+  },
+  "files": [
+    "bin/onemessagebus.js"
+  ],
+  "engines": {
+    "node": ">=18"
+  },
+  "optionalDependencies": {
+    "onemessagebus-cli-linux-x64": "0.4.0",
+    "onemessagebus-cli-linux-arm64": "0.4.0",
+    "onemessagebus-cli-darwin-x64": "0.4.0",
+    "onemessagebus-cli-darwin-arm64": "0.4.0",
+    "onemessagebus-cli-win32-x64": "0.4.0"
+  }
+}