@artblocks/abx-effects 0.1.0-alpha.22 → 0.1.0-alpha.24

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.
Files changed (2) hide show
  1. package/CHANGELOG.md +37 -0
  2. package/package.json +4 -4
package/CHANGELOG.md CHANGED
@@ -1,5 +1,42 @@
1
1
  # @artblocks/abx-effects
2
2
 
3
+ ## 0.1.0-alpha.24
4
+
5
+ ### Patch Changes
6
+
7
+ - Updated dependencies [61503c3]
8
+ - @artblocks/abx-sdk@0.1.0-alpha.24
9
+ - @artblocks/abx-storage@0.1.0-alpha.24
10
+
11
+ ## 0.1.0-alpha.23
12
+
13
+ ### Patch Changes
14
+
15
+ - bd77ba2: Correct the Node floor to 22.13, and refuse to start with a remedy instead of a stack trace.
16
+
17
+ Every package declared `engines.node: ">=22.5.0"` — the version `node:sqlite` was **added**, not the
18
+ version it became usable. It shipped in v22.5.0 behind `--experimental-sqlite` and lost the flag in
19
+ v22.13.0 / v23.4.0. So `npm i -g @artblocks/abx-cli` on Node 22.5 installed silently (the engine
20
+ range was satisfied) and then `abx doctor` — the first command we tell everyone to run — died with a
21
+ raw `ERR_UNKNOWN_BUILTIN_MODULE: No such built-in module: node:sqlite` stack trace naming neither
22
+ abx nor a fix. Reported 2026-08-24; the floor is now `>=22.13.0` everywhere, so npm warns at install
23
+ time.
24
+
25
+ The crash happened while ESM _linked_ `main.ts`'s import graph (`output.ts` →
26
+ `@artblocks/abx-indexer` → `node:sqlite`), before any of our code ran, so no guard inside the CLI
27
+ could have caught it. The published binary is now a deliberately import-free shim (`dist/bin.js`)
28
+ that probes for `node:sqlite` and hands off to `main.js` — it prints the running version, the real
29
+ floor, and the upgrade command. It probes the **capability**, not the version number: an old Node
30
+ launched with `NODE_OPTIONS=--experimental-sqlite` genuinely works, and refusing that would be a
31
+ false negative. `engines` states what we support; the guard blocks only what is actually broken.
32
+
33
+ `abx doctor`'s header now also reports the running Node, since its output is what people paste when
34
+ something is wrong.
35
+
36
+ - Updated dependencies [bd77ba2]
37
+ - @artblocks/abx-storage@0.1.0-alpha.23
38
+ - @artblocks/abx-sdk@0.1.0-alpha.23
39
+
3
40
  ## 0.1.0-alpha.22
4
41
 
5
42
  ### Patch Changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@artblocks/abx-effects",
3
- "version": "0.1.0-alpha.22",
3
+ "version": "0.1.0-alpha.24",
4
4
  "license": "MIT",
5
5
  "description": "ABX Self-Host Toolkit (Layer 3) — the reference effect runner. A deployed, long-running service hosting spine-subscribing effects (render first) behind one harness; stateless via inputsHash addressing. The playwright npm package is a normal (small, browserless) dependency pinned EXACTLY to the Dockerfile.effects base-image tag; browsers install only where captures run (`npx playwright install chromium`).",
6
6
  "type": "module",
@@ -18,7 +18,7 @@
18
18
  ],
19
19
  "sideEffects": false,
20
20
  "engines": {
21
- "node": ">=22.5.0"
21
+ "node": ">=22.13.0"
22
22
  },
23
23
  "repository": {
24
24
  "type": "git",
@@ -41,8 +41,8 @@
41
41
  "dependencies": {
42
42
  "playwright": "1.61.1",
43
43
  "viem": "^2.21.0",
44
- "@artblocks/abx-sdk": "0.1.0-alpha.22",
45
- "@artblocks/abx-storage": "0.1.0-alpha.22"
44
+ "@artblocks/abx-sdk": "0.1.0-alpha.24",
45
+ "@artblocks/abx-storage": "0.1.0-alpha.24"
46
46
  },
47
47
  "scripts": {
48
48
  "build": "tsc -b tsconfig.build.json"