Packages

ata-validator

1.61.3 · 29 Oct 2026MIT21.8k / weekRepositoryHomepagenpmAtom feed

Upgrading ata-validator from 1.51.0 to 1.52.0

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 1.51.0Newest 1.x, Latest1.61.3
0
changes to make
0
advisories fixed
0
new
2
fixes

Release by release

  1. 1.52.0

    11 Oct 20262 fixes
    • fixed

      The generated code walked an object's keys with for...in, which also visits enumerable keys its prototype carries, where the interpreter reads own keys only. A class instance or an object made with Object.create was rejected where additionalProperties is false, and under not that turned into accepting what the interpreter rejects: on the official suite's object data rebuilt over such prototypes, 236 verdicts and 102 error lists differed, two of them accepts. The key loops of both generators now skip keys an object does not own, with the prototype read once per loop; an ordinary object, whose prototype is Object.prototype, takes its keys as before, so JSON.parse output pays nothing. tests/test_inherited_keys.js holds the 2,918 variants. A polluted Object.prototype is not covered: the generated code takes an ordinary object's prototype as clean, as the default validator does.

    • fixed

      The shared runtime (ata-errors.mjs, schema modules, errorRuntimeSource) called its bundled files through a local function named require. A tool that reads the file without scope took require('./interpreter-core') for an import of a file that is not there: knip reported ten unresolved imports in a project that checks its generated sources. The local function has another name now.

4 other lines we could not sort, mostly version bumps

  • A oneOf whose branches each allow only their own properties ({ properties: {...}, additionalProperties: false }, no property in two branches) is answered by the branch the object's first key names instead of trying every branch. Traefik's file-provider schemas, 25 middleware branches, go from 10.8 to 1.2 µs a document. Values that are not objects, and objects with no keys, still try every branch.

    1.52.0

  • A small object definition referenced from many places in a large schema is written as several functions with the same body, each serving at most four references. One function called with objects of dozens of shapes falls off V8's fast property reads; SchemaStore's detekt sends 72 shapes through one rule definition and goes from 6.3 to 1.1 µs a document. Definitions without properties are not copied.

    1.52.0

  • The linear-time pattern engine, which runs the patterns the platform RegExp cannot be trusted with, steps through one flat transition table of 16-bit entries instead of a state object per character: 25 to 35% less per test on SchemaStore's patterns, and less memory than before (17.9 against 21.2 KB per pattern in use). dart-build goes from 2.82 to 1.96 µs a document, popxf from 6.44 to 4.46, apple-app-site-association from 0.73 to 0.50.

    1.52.0

  • A server bundle built with esbuild, Rollup or webpack reads a new ESM entry, index.bundle.mjs, through the module condition, which those bundlers match and Node does not. It imports each tool on its own, as the browser entry does, so the tools an application does not import stay out: an app that imports only Validator goes from 142.8 to 135.0 KB gzipped with esbuild, 150.0 to 141.5 with Rollup and 134.9 to 127.1 with webpack. Node and Bun at run time keep the entries they had, since loading every tool up front cost 7.6 ms in Node before 22.10 and 1.3 ms in Bun. bun build does not match module unless asked: bun build --conditions=module gives 134.7 KB against 142.6.

    1.52.0