Skip to content

chore: release @tskm/core 0.2.1 (compiled fast path) #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ushironoko merged 1 commit into from
Jun 17, 2026
Merged

chore: release @tskm/core 0.2.1 (compiled fast path) #37

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions .changeset/compiled-fast-path.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
"@tskm/core": patch
---

Add an opt-in, experimental compiled validation fast path (Tier-0, no eval). `safeParseCompiled` compiles a schema into a closure tree at construction time, with no `eval`, `new Function`, or codegen, so it runs under a strict CSP and on edge runtimes (Cloudflare Workers, Deno Deploy, Vercel Edge) where JIT codegen is blocked.

- It removes the interpreter's megamorphic per-node dispatch and per-value dataset allocation, winning roughly 1.1x to 2.4x on container schemas across both V8 and JSC, while staying byte-identical to `safeParse` on both success and error paths.
- The interpreter stays the single source of truth. Piped, async, and non-specialized nodes fall back to `~run`, and specialization dispatches on factory identity (`schema.reference`), so a foreign schema with a colliding `type` string keeps running its own `~run`.
- New exports are `safeParseCompiled`, `getCompiledValidate`, and the `Cursor` and `Step` types. A bare top-level primitive should keep using `safeParse` directly.
Loading