@kya-os/checkpoint-express 1.1.0 → 1.1.2
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/CHANGELOG.md +62 -0
- package/dist/index.js +22 -1797
- package/dist/index.mjs +15 -1790
- package/package.json +4 -4
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,67 @@
|
|
|
1
1
|
# @kya-os/checkpoint-express
|
|
2
2
|
|
|
3
|
+
## 1.1.2 — 2026-05-17
|
|
4
|
+
|
|
5
|
+
**Critical rebuild.** 1.1.1 shipped with `engineVerify` bundled inline
|
|
6
|
+
from wasm-runtime@1.0.0 — which had the `(void 0) is not a function`
|
|
7
|
+
tree-shake bug that was later fixed in wasm-runtime@1.1.1 (#2611). Even
|
|
8
|
+
after that wasm-runtime fix, Express consumers were still hitting the
|
|
9
|
+
bug because the broken code was baked into Express's published bundle
|
|
10
|
+
rather than imported transitively at install time.
|
|
11
|
+
|
|
12
|
+
### Fix
|
|
13
|
+
|
|
14
|
+
tsup `external` now lists `@kya-os/checkpoint-wasm-runtime` (and its
|
|
15
|
+
subpath exports) so the wasm-runtime is loaded via Node's runtime
|
|
16
|
+
resolution rather than inlined at bundle time. Fresh installs of
|
|
17
|
+
checkpoint-express@1.1.2 transitively pull whatever wasm-runtime
|
|
18
|
+
version their dep range resolves — currently 1.1.2 (with all the
|
|
19
|
+
SDK-WASM-Bundler-Loader fixes from 1.1.0 → 1.1.2).
|
|
20
|
+
|
|
21
|
+
Bundle proof:
|
|
22
|
+
|
|
23
|
+
```
|
|
24
|
+
$ grep -c "function engineVerify" dist/index.mjs
|
|
25
|
+
0 # ✓ no longer inlined
|
|
26
|
+
|
|
27
|
+
$ grep "from '@kya-os/checkpoint-wasm-runtime" dist/index.mjs
|
|
28
|
+
import { verifyRequest, renderDecisionAsResponse } from '@kya-os/checkpoint-wasm-runtime/orchestrator';
|
|
29
|
+
import { makeSystemClock, ... } from '@kya-os/checkpoint-wasm-runtime/adapters';
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
### Surfaced by
|
|
33
|
+
|
|
34
|
+
Bench-Before-After-1 §3.8 pivot — when the Next.js bench-new path
|
|
35
|
+
proved unstable (see [#2618 SDK-Next.js-Integration-Audit-1](https://github.com/Know-That-Ai/agent-shield/issues/2618)),
|
|
36
|
+
the architect pivoted to Express. Local smoke against the freshly-
|
|
37
|
+
cloned `sites/express-bench-new` immediately hit `(void 0) is not a
|
|
38
|
+
function` in the bundled engineVerify — exposed Express's stale-bundle
|
|
39
|
+
issue that the Next.js path had hidden behind its own bundling layers.
|
|
40
|
+
|
|
41
|
+
### Followup
|
|
42
|
+
|
|
43
|
+
SDK-Next.js-Integration-Audit-1 (#2618) Option B (wasm-bindgen `--target
|
|
44
|
+
bundler`) will eventually let all consumers either bundle or externalize
|
|
45
|
+
wasm-runtime without the (void 0) class of bug. Until then, externalizing
|
|
46
|
+
at the consumer-package level is the right defense.
|
|
47
|
+
|
|
48
|
+
---
|
|
49
|
+
|
|
50
|
+
## 1.1.1 — 2026-05-17
|
|
51
|
+
|
|
52
|
+
Companion patch to `@kya-os/checkpoint-wasm-runtime@1.1.0`. Express
|
|
53
|
+
consumers can already use `withCheckpoint` (Next.js Turbopack was the
|
|
54
|
+
trigger, not Express's bundler-less Node import flow), but this bump
|
|
55
|
+
keeps the wasm-runtime dep range consistent across all checkpoint-\*
|
|
56
|
+
packages.
|
|
57
|
+
|
|
58
|
+
### Internal change
|
|
59
|
+
|
|
60
|
+
- `@kya-os/checkpoint-wasm-runtime` optional-dep changed from exact
|
|
61
|
+
`1.0.0` pin to `^1.1.0` range (via `workspace:^`).
|
|
62
|
+
|
|
63
|
+
---
|
|
64
|
+
|
|
3
65
|
## 1.1.0 — 2026-05-17
|
|
4
66
|
|
|
5
67
|
Closes [SDK-Envelope-Plumbing-1 (#2594)](https://github.com/Know-That-Ai/agent-shield/issues/2594)
|