homegraph 1.1.2 → 1.2.0

package/scripts/local-install.sh

@@ -1,41 +1,41 @@
-#!/usr/bin/env bash
-# Build the current branch and link it as the global `homegraph` for
-# hands-on testing. Replaces any existing global install for as long
-# as the symlink is in place.
-#
-# Usage:
-#   ./scripts/local-install.sh           # build + link
-#   ./scripts/local-install.sh --undo    # unlink + restore the published version
-
-set -euo pipefail
-
-cd "$(dirname "$0")/.."
-
-PKG=$(node -p "require('./package.json').name")
-VERSION=$(node -p "require('./package.json').version")
-BRANCH=$(git rev-parse --abbrev-ref HEAD)
-
-if [ "${1:-}" = "--undo" ]; then
-  echo "→ unlinking ${PKG}"
-  npm unlink -g "${PKG}" >/dev/null 2>&1 || true
-  echo "→ reinstalling published ${PKG}"
-  npm install -g "${PKG}"
-  echo "done: global homegraph -> $(command -v homegraph)"
-  exit 0
-fi
-
-echo "→ building ${PKG} ${VERSION} (${BRANCH})"
-npm run build
-
-echo "→ linking globally"
-npm link
-
-LINKED=$(command -v homegraph || echo "(not on PATH)")
-echo
-echo "✓ global homegraph now points to this branch"
-echo "  binary:  ${LINKED}"
-echo "  branch:  ${BRANCH}"
-echo "  version: ${VERSION}"
-echo
-echo "To restore the published version:"
-echo "  ./scripts/local-install.sh --undo"
+#!/usr/bin/env bash
+# Build the current branch and link it as the global `homegraph` for
+# hands-on testing. Replaces any existing global install for as long
+# as the symlink is in place.
+#
+# Usage:
+#   ./scripts/local-install.sh           # build + link
+#   ./scripts/local-install.sh --undo    # unlink + restore the published version
+
+set -euo pipefail
+
+cd "$(dirname "$0")/.."
+
+PKG=$(node -p "require('./package.json').name")
+VERSION=$(node -p "require('./package.json').version")
+BRANCH=$(git rev-parse --abbrev-ref HEAD)
+
+if [ "${1:-}" = "--undo" ]; then
+  echo "→ unlinking ${PKG}"
+  npm unlink -g "${PKG}" >/dev/null 2>&1 || true
+  echo "→ reinstalling published ${PKG}"
+  npm install -g "${PKG}"
+  echo "done: global homegraph -> $(command -v homegraph)"
+  exit 0
+fi
+
+echo "→ building ${PKG} ${VERSION} (${BRANCH})"
+npm run build
+
+echo "→ linking globally"
+npm link
+
+LINKED=$(command -v homegraph || echo "(not on PATH)")
+echo
+echo "✓ global homegraph now points to this branch"
+echo "  binary:  ${LINKED}"
+echo "  branch:  ${BRANCH}"
+echo "  version: ${VERSION}"
+echo
+echo "To restore the published version:"
+echo "  ./scripts/local-install.sh --undo"

package/scripts/npm-sdk.js

@@ -1,75 +1,75 @@
-'use strict';
-//
-// Programmatic / embedded SDK entry for homegraph (issue #354).
-//
-// The CLI/MCP `bin` (npm-shim.js) execs the per-platform bundle's OWN Node 24 so
-// the tool never depends on the user's runtime. Embedded library consumers are
-// the opposite case: they already run their own Node and just want the compiled
-// API — `require("homegraph")` returning the HomeGraph class et al.
-//
-// The compiled library + its production dependencies (web-tree-sitter,
-// tree-sitter-wasms, …) ship INSIDE the per-platform bundle, at
-//   homegraph-<platform>-<arch>/lib/dist/index.js
-// (with the deps in the sibling lib/node_modules). Re-exporting that bundle keeps
-// the main package thin — no second 50 MB copy of the grammars — while making the
-// SDK work in the consumer's process. Types are a separate concern: the main
-// package ships its own dist/**/*.d.ts tree (pointed at by `types`), built from
-// the same release so it can never skew from the runtime it re-exports.
-//
-// node:sqlite (Node >= 22.5) is required to OPEN a graph, but only lazily inside
-// the SQLite adapter — so loading this module is safe on older Node, and the
-// node:sqlite requirement surfaces with an actionable error only when a DB is
-// actually opened. Heavy extraction additionally wants the bundled launcher's
-// --liftoff-only flag (the WASM Zone-OOM guard, issues #293/#298); an embedded
-// host that drives large indexing should pass that flag to its own Node.
-
-var path = require('path');
-var os = require('os');
-var fs = require('fs');
-
-var target = process.platform + '-' + process.arch; // e.g. darwin-arm64, linux-x64
-var pkg = 'homegraph-' + target;
-
-module.exports = require(resolveLibrary());
-
-// Locate the compiled library entry inside the installed per-platform bundle.
-// Throws an actionable error (rather than a bare MODULE_NOT_FOUND) when no bundle
-// is present, so an embedded consumer knows exactly what to install.
-function resolveLibrary() {
-  // 1) The npm-installed optional dependency — the normal case.
-  try {
-    return require.resolve(pkg + '/lib/dist/index.js');
-  } catch (e) {
-    /* fall through to the self-healed cache */
-  }
-
-  // 2) A bundle the CLI shim self-healed from GitHub Releases into the cache
-  //    (issue #303). Same node/lib/bin layout as the npm package. We only REUSE a
-  //    cached bundle here — unlike the CLI shim we never trigger a network
-  //    download from inside require(), which must stay synchronous and cheap.
-  var cached = cachedLibrary();
-  if (cached) return cached;
-
-  throw new Error(
-    'homegraph: the programmatic API is unavailable because the platform bundle\n' +
-    '(' + pkg + ') is not installed.\n' +
-    'The compiled library ships inside that per-platform optional dependency.\n' +
-    'Fixes:\n' +
-    '  - install from the official npm registry so the matching bundle is fetched:\n' +
-    '      npm i homegraph --registry=https://registry.npmjs.org\n' +
-    '  - or run the CLI once (e.g. `npx homegraph status`) to\n' +
-    '    self-heal the bundle into ~/.homegraph, then require() will find it.'
-  );
-}
-
-function cachedLibrary() {
-  try {
-    var version = require(path.join(__dirname, 'package.json')).version;
-    var base = process.env.HOMEGRAPH_INSTALL_DIR || path.join(os.homedir(), '.homegraph');
-    var lib = path.join(base, 'bundles', target + '-' + version, 'lib', 'dist', 'index.js');
-    if (fs.existsSync(lib)) return lib;
-  } catch (e) {
-    /* no readable cache → caller reports the install guidance */
-  }
-  return null;
-}
+'use strict';
+//
+// Programmatic / embedded SDK entry for homegraph (issue #354).
+//
+// The CLI/MCP `bin` (npm-shim.js) execs the per-platform bundle's OWN Node 24 so
+// the tool never depends on the user's runtime. Embedded library consumers are
+// the opposite case: they already run their own Node and just want the compiled
+// API — `require("homegraph")` returning the HomeGraph class et al.
+//
+// The compiled library + its production dependencies (web-tree-sitter,
+// tree-sitter-wasms, …) ship INSIDE the per-platform bundle, at
+//   homegraph-<platform>-<arch>/lib/dist/index.js
+// (with the deps in the sibling lib/node_modules). Re-exporting that bundle keeps
+// the main package thin — no second 50 MB copy of the grammars — while making the
+// SDK work in the consumer's process. Types are a separate concern: the main
+// package ships its own dist/**/*.d.ts tree (pointed at by `types`), built from
+// the same release so it can never skew from the runtime it re-exports.
+//
+// node:sqlite (Node >= 22.5) is required to OPEN a graph, but only lazily inside
+// the SQLite adapter — so loading this module is safe on older Node, and the
+// node:sqlite requirement surfaces with an actionable error only when a DB is
+// actually opened. Heavy extraction additionally wants the bundled launcher's
+// --liftoff-only flag (the WASM Zone-OOM guard, issues #293/#298); an embedded
+// host that drives large indexing should pass that flag to its own Node.
+
+var path = require('path');
+var os = require('os');
+var fs = require('fs');
+
+var target = process.platform + '-' + process.arch; // e.g. darwin-arm64, linux-x64
+var pkg = 'homegraph-' + target;
+
+module.exports = require(resolveLibrary());
+
+// Locate the compiled library entry inside the installed per-platform bundle.
+// Throws an actionable error (rather than a bare MODULE_NOT_FOUND) when no bundle
+// is present, so an embedded consumer knows exactly what to install.
+function resolveLibrary() {
+  // 1) The npm-installed optional dependency — the normal case.
+  try {
+    return require.resolve(pkg + '/lib/dist/index.js');
+  } catch (e) {
+    /* fall through to the self-healed cache */
+  }
+
+  // 2) A bundle the CLI shim self-healed from GitHub Releases into the cache
+  //    (issue #303). Same node/lib/bin layout as the npm package. We only REUSE a
+  //    cached bundle here — unlike the CLI shim we never trigger a network
+  //    download from inside require(), which must stay synchronous and cheap.
+  var cached = cachedLibrary();
+  if (cached) return cached;
+
+  throw new Error(
+    'homegraph: the programmatic API is unavailable because the platform bundle\n' +
+    '(' + pkg + ') is not installed.\n' +
+    'The compiled library ships inside that per-platform optional dependency.\n' +
+    'Fixes:\n' +
+    '  - install from the official npm registry so the matching bundle is fetched:\n' +
+    '      npm i homegraph --registry=https://registry.npmjs.org\n' +
+    '  - or run the CLI once (e.g. `npx homegraph status`) to\n' +
+    '    self-heal the bundle into ~/.homegraph, then require() will find it.'
+  );
+}
+
+function cachedLibrary() {
+  try {
+    var version = require(path.join(__dirname, 'package.json')).version;
+    var base = process.env.HOMEGRAPH_INSTALL_DIR || path.join(os.homedir(), '.homegraph');
+    var lib = path.join(base, 'bundles', target + '-' + version, 'lib', 'dist', 'index.js');
+    if (fs.existsSync(lib)) return lib;
+  } catch (e) {
+    /* no readable cache → caller reports the install guidance */
+  }
+  return null;
+}