@take-out/scripts 0.4.14 → 0.4.16

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@take-out/scripts",
-  "version": "0.4.14",
+  "version": "0.4.16",
   "type": "module",
   "main": "./src/cmd.ts",
   "sideEffects": false,
@@ -29,8 +29,8 @@
   },
   "dependencies": {
     "@clack/prompts": "^0.8.2",
-    "@take-out/helpers": "0.4.14",
-    "@take-out/run": "0.4.14",
+    "@take-out/helpers": "0.4.16",
+    "@take-out/run": "0.4.16",
     "picocolors": "^1.1.1"
   }
 }

package/src/ensure-zero-sqlite.ts

@@ -8,14 +8,23 @@ await cmd`ensure zero-sqlite3 native module is built`.run(async ({ $, fs }) => {
     return
   }
 
-  // bun trustedDependencies doesn't reliably build native modules
-  const result = await $`cd node_modules/@rocicorp/zero-sqlite3 && npm run build-release`
+  // bun trustedDependencies doesn't reliably run zero-sqlite3's install script,
+  // so build/fetch the native module ourselves. run the package's OWN install
+  // chain (`npm run install` = `prebuild-install || <binding exists?> ||
+  // node-gyp rebuild`), which prefers the PREBUILT binary and only source-builds
+  // as a last resort. @rocicorp/zero-sqlite3 >=1.1.2 is prebuilt-ONLY — its npm
+  // tarball omits generated headers (e.g. unicode_case_data.h), so a direct
+  // `npm run build-release` (node-gyp) fails; prebuild-install is the supported
+  // path. success is "the binding now exists" (the install chain can exit
+  // non-zero from a failed prebuild-install fallback even when an earlier step
+  // already produced the binding).
+  const result = await $`cd node_modules/@rocicorp/zero-sqlite3 && npm run install`
     .quiet()
     .nothrow()
 
-  if (result.exitCode !== 0) {
+  if (!fs.existsSync(SQLITE_NODE_PATH)) {
     console.error(
-      'zero-sqlite3 build failed, will fall back to wasm:',
+      'zero-sqlite3 native module unavailable, will fall back to wasm:',
       result.stderr.toString(),
     )
   }