@carllee1983/dbcli 1.55.0 → 1.55.1

package/CHANGELOG.md

@@ -5,6 +5,12 @@ All notable changes to dbcli are documented here.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.55.1] - 2026-08-13 - The Bun-missing warning actually reaches the user
+
+### Fixed
+
+- **v1.55.0's post-install check could never fail, and npm therefore never showed it.** Verified against the published package in `docker run --rm node:22`: `npm install -g @carllee1983/dbcli` printed `added 131 packages` and nothing else, and `dbcli --version` then died with `/usr/bin/env: 'bun': No such file or directory` — exactly the experience the check was added to prevent. Two causes stacked. npm hides lifecycle-script output unless the script exits non-zero (the message was there all along under `--foreground-scripts`), and the `postinstall` command ended in `|| exit 0`, which swallowed any exit code the check could produce. The trailing `|| exit 0` is gone, and `scripts/postinstall-check-bun.mjs` now exits 1 when Bun is missing **and** `npm_config_global` is `true`. A global install is the case whose entire point is a runnable `dbcli`, so it fails loudly with the reason, and npm rolls the `bin` back rather than leaving a dead executable on `PATH` (verified: `command -v dbcli` finds nothing afterwards). A dependency install is left alone — that is the `./agent-core` consumer, who needs no Bun, and it still exits 0 with the subpath export importable from Node. `tests/integration/runtime-contract.test.ts` pins both outcomes and asserts the published `postinstall` command contains no `exit 0` mask, since a check that cannot fail is indistinguishable from one that passes (#65).
+
 ## [1.55.0] - 2026-08-13 - Packaging: the declared runtime matches the artifact
 
 ### Removed

package/README.dev.md

@@ -108,7 +108,7 @@ Then ship a patch version with the fix. Prefer **deprecate** over **unpublish**
 - **`prepublishOnly`:** `bun run build` so `dist/cli.mjs` matches current source.
 - **`engines`:** Declares `bun >= 1.3.3` only. `node` was removed because the published bundles cannot run on Node: `dist/cli.mjs` dynamic-imports the extensionless `./cli-runtime` (Bun's resolver appends `.mjs`, Node's does not) and `dist/core.mjs` calls Bun globals. `tests/integration/runtime-contract.test.ts` fails if `engines.node` comes back without the bundles being fixed to match, and if `dist/agent-core.mjs` — the one entry point that is Node-importable — regresses. See `docs/adr/0008-dbcli-is-a-bun-program-and-engines-says-so.md`.
 - **Shebang:** `scripts/build.ts` prepends `#!/usr/bin/env bun` to `dist/cli.mjs`; the `bin` field in `package.json` points at that file.
-- **`postinstall`:** `scripts/postinstall-check-bun.mjs` warns (never fails) when Bun is missing after install — npm ignores `engines.bun`, so this is the only signal an npm-only machine gets before `dbcli` refuses to start. The script command is `bun … || node … || exit 0` so it runs whichever runtime is present: Bun-only machines have no `node` to invoke it with, and a hard `node` dependency there would break the primary install path.
+- **`postinstall`:** `scripts/postinstall-check-bun.mjs` reports a missing Bun — npm ignores `engines.bun`, so this is the only signal an npm-only machine gets before `dbcli` refuses to start. The command is `bun … || node …` so it runs under whichever runtime is present: Bun-only machines have no `node` to invoke it with, and a hard `node` dependency there would break the primary install path. It must **not** end in `|| exit 0`; v1.55.0 shipped with that mask and npm, which hides lifecycle output unless a script fails, therefore showed nothing at all. On a global install (`npm_config_global === 'true'`) a missing Bun exits 1, so the reason is printed and npm rolls the `bin` back; a dependency install only warns, because that is the `./agent-core` consumer. Both outcomes are pinned in `tests/integration/runtime-contract.test.ts`.
 - **Live DB tests:** `tests/integration/live-db.test.ts` uses project `.dbcli` by default or `LIVE_DB_CONFIG_PATH` when you point at another config directory. Set `SKIP_INTEGRATION_TESTS=true` to skip all integration tests.
 
 For contributor workflow and release process, see **[CONTRIBUTING.md](./CONTRIBUTING.md)** and the main **[README.md](./README.md)** Development section.

package/dist/cli-runtime.mjs

@@ -51,7 +51,7 @@ var package_default;
 var init_package = __esm(() => {
   package_default = {
     name: "@carllee1983/dbcli",
-    version: "1.55.0",
+    version: "1.55.1",
     description: "Database CLI for AI agents",
     type: "module",
     publishConfig: {
@@ -114,7 +114,7 @@ var init_package = __esm(() => {
       "LICENSE"
     ],
     scripts: {
-      postinstall: "bun scripts/postinstall-check-bun.mjs || node scripts/postinstall-check-bun.mjs || exit 0",
+      postinstall: "bun scripts/postinstall-check-bun.mjs || node scripts/postinstall-check-bun.mjs",
       dev: "bun run src/cli.ts",
       build: "bun run scripts/build.ts",
       "build:determinism": "bun run scripts/check-build-determinism.ts",

package/dist/cli.mjs

@@ -3,7 +3,7 @@
 // package.json
 var package_default = {
   name: "@carllee1983/dbcli",
-  version: "1.55.0",
+  version: "1.55.1",
   description: "Database CLI for AI agents",
   type: "module",
   publishConfig: {
@@ -66,7 +66,7 @@ var package_default = {
     "LICENSE"
   ],
   scripts: {
-    postinstall: "bun scripts/postinstall-check-bun.mjs || node scripts/postinstall-check-bun.mjs || exit 0",
+    postinstall: "bun scripts/postinstall-check-bun.mjs || node scripts/postinstall-check-bun.mjs",
     dev: "bun run src/cli.ts",
     build: "bun run scripts/build.ts",
     "build:determinism": "bun run scripts/check-build-determinism.ts",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@carllee1983/dbcli",
-  "version": "1.55.0",
+  "version": "1.55.1",
   "description": "Database CLI for AI agents",
   "type": "module",
   "publishConfig": {
@@ -63,7 +63,7 @@
     "LICENSE"
   ],
   "scripts": {
-    "postinstall": "bun scripts/postinstall-check-bun.mjs || node scripts/postinstall-check-bun.mjs || exit 0",
+    "postinstall": "bun scripts/postinstall-check-bun.mjs || node scripts/postinstall-check-bun.mjs",
     "dev": "bun run src/cli.ts",
     "build": "bun run scripts/build.ts",
     "build:determinism": "bun run scripts/check-build-determinism.ts",

package/scripts/postinstall-check-bun.mjs

@@ -31,19 +31,31 @@ function bunIsAvailable() {
   }
 }
 
+// npm hides lifecycle-script output unless the script fails (verified on npm 10.9.8:
+// a warning printed here is invisible without --foreground-scripts). So a global
+// install — the one whose whole purpose is a working `dbcli` on PATH — exits non-zero
+// to make the reason visible, and npm rolls the broken executable back. A local install
+// stays silent and succeeds: that is the `./agent-core` consumer, who needs no Bun.
+const isGlobalInstall = process.env.npm_config_global === 'true'
+
 if (!bunIsAvailable()) {
-  console.warn(
-    [
-      '',
-      'dbcli: Bun was not found on PATH.',
-      '',
-      "  The package installed, but dbcli's executable runs under Bun (its shebang is",
-      '  `#!/usr/bin/env bun`), so `dbcli` will not start until Bun 1.3.3+ is installed:',
-      '',
-      `    ${BUN_INSTALL_HINT}`,
-      '',
-      '  The ./agent-core subpath export is importable from Node without Bun.',
-      '',
-    ].join('\n')
-  )
+  const message = [
+    '',
+    'dbcli: Bun was not found on PATH.',
+    '',
+    "  dbcli's executable runs under Bun (its shebang is `#!/usr/bin/env bun`), so it",
+    '  cannot start until Bun 1.3.3+ is installed:',
+    '',
+    `    ${BUN_INSTALL_HINT}`,
+    '',
+    '  Then re-run the install. The ./agent-core subpath export is importable from',
+    '  Node without Bun, and installing it as a project dependency does not need this.',
+    '',
+  ].join('\n')
+
+  if (isGlobalInstall) {
+    console.error(message)
+    process.exit(1)
+  }
+  console.warn(message)
 }