crispy-recall 0.2.0 → 0.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/stop-hook.js CHANGED
@@ -976,7 +976,10 @@ var BindingLoadError = class extends Error {
976
976
  constructor(dbPath2, cause) {
977
977
  super(
978
978
  `recall: failed to load the better-sqlite3 native binding while opening ${dbPath2}: ${cause.message}
979
- The binding is ABI-locked to the Node it was built for \u2014 run \`recall doctor\` (usually fixed by re-running \`recall install\`).`
979
+ The native SQLite binding is ABI-locked to the Node it was built for. This is usually one of:
980
+ \u2022 recall is running under a different Node than the one npm installed it with (e.g. Homebrew node vs nvm) \u2014 reinstall with \`npm install -g crispy-recall\` using the node on your PATH, then \`recall install\`.
981
+ \u2022 no prebuilt binary matched your Node version and it could not compile \u2014 use Node 22 LTS or 24+ (Node 23 has no prebuilt SQLite binding), and on macOS make sure Xcode Command Line Tools are installed (\`xcode-select --install\`).
982
+ Run \`recall doctor\` for details.`
980
983
  );
981
984
  this.dbPath = dbPath2;
982
985
  this.cause = cause;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "crispy-recall",
3
- "version": "0.2.0",
3
+ "version": "0.2.1",
4
4
  "description": "Local session transcript memory for Claude Code and Codex — search past sessions with FTS5 + semantic vectors.",
5
5
  "license": "MIT",
6
6
  "author": "Sylvester Wong",
@@ -31,7 +31,7 @@
31
31
  "THIRD-PARTY-LICENSES"
32
32
  ],
33
33
  "engines": {
34
- "node": ">=22.16"
34
+ "node": ">=22.16.0 <23 || >=24.0.0"
35
35
  },
36
36
  "scripts": {
37
37
  "build": "node scripts/build.mjs",