ata-validator
1.61.3 · 29 Oct 2026MIT21.8k / weekRepositoryHomepagenpmAtom feed
Upgrading ata-validator from 1.12.1 to 1.13.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 0
- changes to make
- 0
- advisories fixed
- 1
- new
- 0
- fixes
Release by release
- new
ata-validator/aot: the standalone emitters (toStandalone,toStandaloneModule,bundle,bundleStandalone,bundleCompact,loadBundle) as an explicit, typed import. In Node it is the same module the statics use; in a browser it is the way to opt back into emission without paying for it on pages that never emit.
- new
1 other line we could not sort, mostly version bumps
- 1.13.0
The default browser bundle stops carrying the AOT emitters.
lib/aot.jshas promised a browser stub via the package.jsonbrowserfield since the fs-free build, but the mapping was never actually in the field, so every browser bundle shipped the emitters and the embedded safe-regex engine source they pull in, along with the native walker's routing table that only matters when the native addon loads. Both now map to stubs. Emitting validators in a browser still works, through the newata-validator/aotentry, and theValidator.bundle*statics in a browser bundle throw a message that points there;Validator.loadBundlekeeps working in the default bundle, since loading a bundle somebody already built is a runtime act. Measured with the schema-benchmarks rolldown pipeline: minified and gzipped 73,491 to 64,812 bytes, 11.8 percent smaller. The browser-imports guard now bans a token from each excluded file so the mapping cannot regress silently.