ata-validator 1.36.0 → 1.36.1

package/README.md

@@ -101,16 +101,15 @@ file.
 | Bundle (gzipped) | simple | 1.3 KB | 58.1 KB | 43.9x smaller |
 | Bundle (gzipped) | complex | 7.8 KB | 58.1 KB | 7.4x smaller |
 | Bundle (gzipped) | nested | 4.5 KB | 58.1 KB | 12.9x smaller |
-| Cold start | simple | 22 ms | 44 ms | 2.0x faster |
-| Throughput (1M ops) | simple | 266 Mops/s | 109 Mops/s | 2.4x faster |
-| Compile time | simple | 19 µs | 1.67 ms | 87x faster |
+| Cold start | simple | 22 ms | 40 ms | 1.8x faster |
+| Throughput (1M ops) | simple | 269 Mops/s | 116 Mops/s | 2.3x faster |
+| Compile time | simple | 19 µs | 1.63 ms | 85x faster |
 
 The runtime column is the default validator most frameworks ship. Reproduce on your machine
 with `npm run bench:aot-vs-ajv`. Numbers from one run on Apple M4 Pro, Node 25.2.1, 2026-09-28,
-on ata-validator 1.33.1. The runtime column's bundle measured 52.7 KB on the previous run and
-58.1 KB now, with ata's modules unchanged in size. Across three runs throughput moved
-between 231 and 280 Mops/s against 97 to 109, cold start between 21 and 22 ms against 40 to 44,
-and the compile ratio between 80x and 87x. The throughput row times a single one-million-call
+on ata-validator 1.36.0. Across four runs throughput moved between 213 and 269 Mops/s against
+94 to 116, cold start between 21 and 22 ms against 40 to 42, and the compile ratio between 79x
+and 90x. The throughput row times a single one-million-call
 loop of a few milliseconds, so it moves the most from run to run; treat the last three rows as
 an order of magnitude rather than a constant.
 
@@ -240,21 +239,21 @@ is the most common way to get a misleading number out of this library.
 
 | | compiled with `ata build` | runtime `new Validator(schema)` |
 |---|---|---|
-| In a bundle, gzipped | **2.2 KB** | 93.2 KB |
-| Time to a served request | **3.5 ms** | 7.7 ms |
+| In a bundle, gzipped | **2.2 KB** | 95.6 KB |
+| Time to a served request | **3.5 ms** | 7.8 ms |
 | Schema known when | build time | any time |
 
 The bundle row is the ten-field user schema in
 `tests/fixtures/error-dx/user.schema.json`, every export of the compiled module against
-`new Validator(schema)`, built with `bun build --minify --target=browser` on ata 1.35.0.
-The startup row is a Hono route on Bun 1.4, best of seven, median of three rounds, from
+`new Validator(schema)`, built with `bun build --minify --target=browser` on ata 1.36.0.
+The startup row is a Hono route on Bun 1.4, median of nine interleaved runs, from
 `benchmark/bundle`, against 3.5 ms for the same app doing no validation at all, so the
 compiled path costs nothing measurable to start. The runtime figure is what it is because
 a schema that arrives at run time can use any keyword, so the whole engine has to be
 there. The compiled module imports nothing and contains only the checks your schema asks
 for.
 
-**On a server, use whichever fits your schemas.** 93 KB of JavaScript on a Node or Bun
+**On a server, use whichever fits your schemas.** 96 KB of JavaScript on a Node or Bun
 process is not a cost anyone notices, and the runtime API is the simpler thing to reach
 for. Speed is the same either way once warm.
 
@@ -486,7 +485,7 @@ const v = new Validator(schema, {
 
 ### Build-time compile (`ata compile`)
 
-The `ata` CLI turns a JSON Schema file into a self-contained JavaScript module. No runtime dependency on `ata-validator`, so only the generated validator ships to the browser. For the ten-field user schema in `tests/fixtures/error-dx/user.schema.json` the module is 2.2 KB gzipped, full error detail included, against 93.2 KB for the runtime bundled for the browser.
+The `ata` CLI turns a JSON Schema file into a self-contained JavaScript module. No runtime dependency on `ata-validator`, so only the generated validator ships to the browser. For the ten-field user schema in `tests/fixtures/error-dx/user.schema.json` the module is 2.2 KB gzipped, full error detail included, against 95.6 KB for the runtime bundled for the browser.
 
 ```bash
 npx ata compile schemas/user.json -o src/generated/user.validator.mjs
@@ -528,11 +527,11 @@ npx ata build 'schemas/*.json' --out-dir build/validators --check
 Run with `--watch` during development for incremental rebuilds.
 
 Bundle sizes for the 10-field user schema in `tests/fixtures/error-dx/user.schema.json`,
-minified and gzipped, measured with `bun build --minify --target=browser` on ata 1.35.0:
+minified and gzipped, measured with `bun build --minify --target=browser` on ata 1.36.0:
 
 | What the app imports | Size | Notes |
 |---|---|---|
-| `Validator` from `ata-validator` | 93.2 KB | The compiler ships with it, because a runtime schema can use any keyword |
+| `Validator` from `ata-validator` | 95.6 KB | The compiler ships with it, because a runtime schema can use any keyword |
 | `isValid` from the compiled module | **1.3 KB** | Nothing else is reachable, so the error collector is dropped |
 | `validate` from the compiled module | **2.0 KB** | Adds the detailed error collector |
 
@@ -541,6 +540,16 @@ bundling it makes no difference: importing only `isValid` already leaves the err
 collector unreachable, and a bundler drops it. Use the flag to cut the file on disk,
 not to cut what ships.
 
+To get the compiled module without changing code written against the runtime API, use
+`compileAway` in [`@ata-project/unplugin`](https://github.com/ata-core/unplugin-ata): a
+`new Validator(schema)` whose schema is known at build time is replaced with the compiled
+module wrapped by `fromCompiled()` from `ata-validator/compiled`, which answers `validate()`,
+`isValidObject()`, `validateJSON()` and `isValidJSON()` as the runtime does, defaults and errors
+included. For the plugin's three-schema test entry a minified Vite build goes from 115.7 KB to
+15.5 KB gzipped. In Node, loading the wrapper and a compiled module and answering the first two
+checks takes 1.12 ms where the runtime takes 6.63 ms (median of 15 fresh processes). Across
+SchemaStore's 977 schemas, 725 can be compiled away; the rest stay on the runtime.
+
 Programmatic API if you prefer to script it:
 
 ```javascript
@@ -557,7 +566,7 @@ through a `setFormats()` export the module carries. `docs/API.md` has the
 details.
 
 **Fastify startup, 10 route schemas, from a cold process to the first validated request:
-ajv 20.2 ms, ata 2.7 ms, no build step required.** ata registers in 0.2 ms of that and
+ajv 19.9 ms, ata 2.9 ms, no build step required.** ata registers in 0.5 ms of that and
 compiles on the first request, so counting only registration would overstate the gap.
 Reproduce with `node benchmark/bench_fastify_boot.mjs`.
 

package/lib/validator-core.js

@@ -218,7 +218,9 @@ function codegenAvailable() {
 // Schema compilation cache: same schema string -> reuse compiled functions
 const _compileCache = new Map();
 // Generated preprocess passes, keyed like _compileCache plus the options that
-// shape the pass. `null` records that the generator produced none.
+// shape the pass. Only passes that exist are kept: a schema with nothing to
+// rewrite answers `null` quickly, and keeping that answer held its key, the
+// whole schema text, for every such validator, 0.2 KB each.
 const _preprocessCache = new Map();
 
 // Object identity cache: same schema object reference -> reuse entire compiled state
@@ -908,7 +910,7 @@ class Validator {
       if (hit !== undefined) preprocess = hit;
       else {
         preprocess = _codegen.buildPreprocess(preprocessSchema, options) || null;
-        if (ppKey !== null) _preprocessCache.set(ppKey, preprocess);
+        if (ppKey !== null && preprocess !== null) _preprocessCache.set(ppKey, preprocess);
       }
     }
     if (!preprocess) {

package/lib/version.js

@@ -7,4 +7,4 @@
 //
 // Kept in lockstep with package.json by `tests/test_version_sync.js`.
 
-module.exports = '1.36.0';
+module.exports = '1.36.1';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ata-validator",
-  "version": "1.36.0",
+  "version": "1.36.1",
   "description": "JSON Schema validation that compiles for speed and still runs where code generation is blocked. Compiled and interpreted engines answer identically at 100% of the official suite. TypeScript inference, Standard Schema V1, and a build step that emits dependency-free modules.",
   "main": "index.js",
   "module": "index.mjs",
@@ -134,13 +134,13 @@
     "LICENSE"
   ],
   "optionalDependencies": {
-    "@ata-validator/native-darwin-arm64": "1.36.0",
-    "@ata-validator/native-darwin-x64": "1.36.0",
-    "@ata-validator/native-linux-arm64-gnu": "1.36.0",
-    "@ata-validator/native-linux-arm64-musl": "1.36.0",
-    "@ata-validator/native-linux-x64-gnu": "1.36.0",
-    "@ata-validator/native-linux-x64-musl": "1.36.0",
-    "@ata-validator/native-win32-x64": "1.36.0"
+    "@ata-validator/native-darwin-arm64": "1.36.1",
+    "@ata-validator/native-darwin-x64": "1.36.1",
+    "@ata-validator/native-linux-arm64-gnu": "1.36.1",
+    "@ata-validator/native-linux-arm64-musl": "1.36.1",
+    "@ata-validator/native-linux-x64-gnu": "1.36.1",
+    "@ata-validator/native-linux-x64-musl": "1.36.1",
+    "@ata-validator/native-win32-x64": "1.36.1"
   },
   "peerDependencies": {
     "yaml": "^2.0.0"