typescript-runtime-type-benchmarks
typescript-runtime-type-benchmarks copied to clipboard
moltar
📊 Benchmark Comparison of Packages with Runtime Validation and TypeScript Support
In an serverless environment like a Cloudflare worker, schemas may need to be created on every request. This benchmark doesn't take that into account. I propose adding a new suite...
Node.js v16 and v18 already reached EOL I want to propose removing support for node 16 and 18, it's already creating problem for us where we have to stay on...
The current benchmark viewer uses unpkg.com to load its dependencies. That was the easiest solution for me at the time I wrote it (a time where huge webpack configs, commonsj...
https://dev.to/samchon/bun-is-up-to-20x-slower-than-nodejs-in-logic-operations-305d Could be a good benchmark to add. @kravetsone
As in https://github.com/moltar/typescript-runtime-type-benchmarks/pull/1612 I would suggest using [tsx](https://tsx.is/)
It's very difficult to tell which bar belongs to which runtime in the chart. It would be good add a label so it's clear. Ideally, it would be formatted as...
Arktype supports also a strict assertions which can be used per [object](https://arktype.io/docs/objects#properties-undeclared) or also [globally](https://arktype.io/docs/configuration#onundeclaredkey).
Node 16 has been EoL for a long time (2023-09-11)! Node 18 is going to be EoL very soon too (2025-04-30). https://github.com/nodejs/Release
https://github.com/standard-schema/standard-schema Tag projects using `standard-schema`.