@venturewild/workspace 0.4.2 → 0.5.1

package/server/src/daemon-bin.mjs

@@ -1,110 +1,110 @@
-// Locates the bmo-sync-daemon binary for the current platform.
-//
-// wild-workspace ships the daemon as a per-platform npm subpackage
-// (@venturewild/workspace-daemon-<tag>, biome pattern). The resolver walks a
-// lookup chain so it works both in development (a locally built binary in
-// vendor/ or on PATH) and in a published install (the platform subpackage).
-
-import { existsSync, readFileSync } from 'node:fs';
-import path from 'node:path';
-import url from 'node:url';
-import { createRequire } from 'node:module';
-
-const __dirname = path.dirname(url.fileURLToPath(import.meta.url));
-const require = createRequire(import.meta.url);
-
-/** `<platform>-<arch>` token, e.g. `win32-x64`, `darwin-arm64`, `linux-x64`. */
-export function platformTag() {
-  return `${process.platform}-${process.arch}`;
-}
-
-/** Daemon binary file name for the current platform. */
-export function daemonBinaryName() {
-  return process.platform === 'win32' ? 'bmo-sync-daemon.exe' : 'bmo-sync-daemon';
-}
-
-/**
- * Resolve the daemon binary. Lookup order:
- *   1. WILD_WORKSPACE_DAEMON_BIN — explicit override (must exist, or null).
- *   2. the per-platform npm subpackage `@venturewild/workspace-daemon-<tag>`.
- *   3. a local `vendor/bmo-sync-daemon-<tag>/<bin>` dir (dev builds land here).
- *   4. the bare binary name — let the OS resolve it on PATH at spawn time.
- *
- * Returns `{ path, source }`. `source` is one of `env` | `subpackage` |
- * `vendor` | `path`. Returns `null` only when an explicit override is set
- * but missing — every other case falls through to the PATH last resort.
- *
- * @param {{ env?: NodeJS.ProcessEnv, vendorRoot?: string }} [opts]
- */
-export function resolveDaemonBinary({ env = process.env, vendorRoot, requireResolve } = {}) {
-  const binName = daemonBinaryName();
-  const tag = platformTag();
-  // Injected seam: lets a test simulate "the platform subpackage isn't
-  // installed" deterministically, regardless of what's in this machine's
-  // node_modules (the win32-x64 subpackage IS present on a Windows dev box).
-  const resolvePkg = requireResolve || ((id) => require.resolve(id));
-
-  // 1. explicit override — if set but missing, that's an error, not a miss.
-  const override = env.WILD_WORKSPACE_DAEMON_BIN;
-  if (override) {
-    return existsSync(override) ? { path: override, source: 'env' } : null;
-  }
-
-  // 2. per-platform npm subpackage — resolve via its package.json so the
-  //    lookup doesn't depend on an `exports` map for the binary file.
-  try {
-    const pkgJson = resolvePkg(`@venturewild/workspace-daemon-${tag}/package.json`);
-    const candidate = path.join(path.dirname(pkgJson), binName);
-    if (existsSync(candidate)) return { path: candidate, source: 'subpackage' };
-  } catch {
-    // subpackage not installed — fall through
-  }
-
-  // 3. local vendor dir (a dev build of the daemon drops the binary here).
-  const root = vendorRoot || path.resolve(__dirname, '..', '..', 'vendor');
-  const vendor = path.join(root, `bmo-sync-daemon-${tag}`, binName);
-  if (existsSync(vendor)) return { path: vendor, source: 'vendor' };
-
-  // 4. last resort — spawn by name and let PATH resolve it.
-  return { path: binName, source: 'path' };
-}
-
-/**
- * The version of the INSTALLED per-platform daemon subpackage (e.g. `"0.1.3"`),
- * or null when it can't be determined (resolved via PATH/vendor, or not found).
- * Used by the supervisor to detect a stale running daemon after an auto-update
- * (the daemon's own /health doesn't report a version), so it can recycle it.
- */
-export function resolveDaemonVersion({ env = process.env, requireResolve } = {}) {
-  const tag = platformTag();
-  const resolvePkg = requireResolve || ((id) => require.resolve(id));
-  try {
-    const pkgJson = resolvePkg(`@venturewild/workspace-daemon-${tag}/package.json`);
-    const parsed = JSON.parse(readFileSync(pkgJson, 'utf8'));
-    return typeof parsed.version === 'string' ? parsed.version : null;
-  } catch {
-    return null;
-  }
-}
-
-/**
- * The daemon version the INSTALLED meta package PINS for this platform — read
- * from the meta `package.json`'s optionalDependencies. This is the version
- * `npm i -g @venturewild/workspace@<v>` is SUPPOSED to have pulled onto disk.
- * Comparing it to resolveDaemonVersion() catches the go-live failure where the
- * meta package updated but its daemon optionalDependency on disk lagged behind
- * (the tangled Windows dev box stuck on the @0.2.0-era daemon). Returns the
- * pinned version string, or null when it can't be read. Self-contained: reads the
- * meta package.json that ships two dirs up from this file.
- */
-export function expectedDaemonVersion({ metaPkgPath } = {}) {
-  const tag = platformTag();
-  try {
-    const pkg = metaPkgPath || path.resolve(__dirname, '..', '..', 'package.json');
-    const parsed = JSON.parse(readFileSync(pkg, 'utf8'));
-    const v = parsed?.optionalDependencies?.[`@venturewild/workspace-daemon-${tag}`];
-    return typeof v === 'string' ? v.replace(/^[~^]/, '') : null;
-  } catch {
-    return null;
-  }
-}
+// Locates the bmo-sync-daemon binary for the current platform.
+//
+// wild-workspace ships the daemon as a per-platform npm subpackage
+// (@venturewild/workspace-daemon-<tag>, biome pattern). The resolver walks a
+// lookup chain so it works both in development (a locally built binary in
+// vendor/ or on PATH) and in a published install (the platform subpackage).
+
+import { existsSync, readFileSync } from 'node:fs';
+import path from 'node:path';
+import url from 'node:url';
+import { createRequire } from 'node:module';
+
+const __dirname = path.dirname(url.fileURLToPath(import.meta.url));
+const require = createRequire(import.meta.url);
+
+/** `<platform>-<arch>` token, e.g. `win32-x64`, `darwin-arm64`, `linux-x64`. */
+export function platformTag() {
+  return `${process.platform}-${process.arch}`;
+}
+
+/** Daemon binary file name for the current platform. */
+export function daemonBinaryName() {
+  return process.platform === 'win32' ? 'bmo-sync-daemon.exe' : 'bmo-sync-daemon';
+}
+
+/**
+ * Resolve the daemon binary. Lookup order:
+ *   1. WILD_WORKSPACE_DAEMON_BIN — explicit override (must exist, or null).
+ *   2. the per-platform npm subpackage `@venturewild/workspace-daemon-<tag>`.
+ *   3. a local `vendor/bmo-sync-daemon-<tag>/<bin>` dir (dev builds land here).
+ *   4. the bare binary name — let the OS resolve it on PATH at spawn time.
+ *
+ * Returns `{ path, source }`. `source` is one of `env` | `subpackage` |
+ * `vendor` | `path`. Returns `null` only when an explicit override is set
+ * but missing — every other case falls through to the PATH last resort.
+ *
+ * @param {{ env?: NodeJS.ProcessEnv, vendorRoot?: string }} [opts]
+ */
+export function resolveDaemonBinary({ env = process.env, vendorRoot, requireResolve } = {}) {
+  const binName = daemonBinaryName();
+  const tag = platformTag();
+  // Injected seam: lets a test simulate "the platform subpackage isn't
+  // installed" deterministically, regardless of what's in this machine's
+  // node_modules (the win32-x64 subpackage IS present on a Windows dev box).
+  const resolvePkg = requireResolve || ((id) => require.resolve(id));
+
+  // 1. explicit override — if set but missing, that's an error, not a miss.
+  const override = env.WILD_WORKSPACE_DAEMON_BIN;
+  if (override) {
+    return existsSync(override) ? { path: override, source: 'env' } : null;
+  }
+
+  // 2. per-platform npm subpackage — resolve via its package.json so the
+  //    lookup doesn't depend on an `exports` map for the binary file.
+  try {
+    const pkgJson = resolvePkg(`@venturewild/workspace-daemon-${tag}/package.json`);
+    const candidate = path.join(path.dirname(pkgJson), binName);
+    if (existsSync(candidate)) return { path: candidate, source: 'subpackage' };
+  } catch {
+    // subpackage not installed — fall through
+  }
+
+  // 3. local vendor dir (a dev build of the daemon drops the binary here).
+  const root = vendorRoot || path.resolve(__dirname, '..', '..', 'vendor');
+  const vendor = path.join(root, `bmo-sync-daemon-${tag}`, binName);
+  if (existsSync(vendor)) return { path: vendor, source: 'vendor' };
+
+  // 4. last resort — spawn by name and let PATH resolve it.
+  return { path: binName, source: 'path' };
+}
+
+/**
+ * The version of the INSTALLED per-platform daemon subpackage (e.g. `"0.1.3"`),
+ * or null when it can't be determined (resolved via PATH/vendor, or not found).
+ * Used by the supervisor to detect a stale running daemon after an auto-update
+ * (the daemon's own /health doesn't report a version), so it can recycle it.
+ */
+export function resolveDaemonVersion({ env = process.env, requireResolve } = {}) {
+  const tag = platformTag();
+  const resolvePkg = requireResolve || ((id) => require.resolve(id));
+  try {
+    const pkgJson = resolvePkg(`@venturewild/workspace-daemon-${tag}/package.json`);
+    const parsed = JSON.parse(readFileSync(pkgJson, 'utf8'));
+    return typeof parsed.version === 'string' ? parsed.version : null;
+  } catch {
+    return null;
+  }
+}
+
+/**
+ * The daemon version the INSTALLED meta package PINS for this platform — read
+ * from the meta `package.json`'s optionalDependencies. This is the version
+ * `npm i -g @venturewild/workspace@<v>` is SUPPOSED to have pulled onto disk.
+ * Comparing it to resolveDaemonVersion() catches the go-live failure where the
+ * meta package updated but its daemon optionalDependency on disk lagged behind
+ * (the tangled Windows dev box stuck on the @0.2.0-era daemon). Returns the
+ * pinned version string, or null when it can't be read. Self-contained: reads the
+ * meta package.json that ships two dirs up from this file.
+ */
+export function expectedDaemonVersion({ metaPkgPath } = {}) {
+  const tag = platformTag();
+  try {
+    const pkg = metaPkgPath || path.resolve(__dirname, '..', '..', 'package.json');
+    const parsed = JSON.parse(readFileSync(pkg, 'utf8'));
+    const v = parsed?.optionalDependencies?.[`@venturewild/workspace-daemon-${tag}`];
+    return typeof v === 'string' ? v.replace(/^[~^]/, '') : null;
+  } catch {
+    return null;
+  }
+}