🚨 Exciting update! Our Schema Benchmarks OSS project now has a dedicated section for Standard Schema.
Check it out and discover how fast your favorite Standard Schema libraries like @valibot.dev, @zod.dev, @arktype.io, Effect and more really are! 📈
an update to this:
i noticed a discrepancy between our zod benchmark and zod's docs, namely that we were using a default import and the docs show a namespace import.
updating our benchmark to match the docs brought zod down to a much more reasonable 16KB.
quick update re: Typebox - it had been slowed down by a feature in v1 that attempts to coerce an invalid value into a valid one. v1.1 now makes that feature opt-in.
here's an updated set of results, with a vast improvement in typebox's performance:
it's certainly one of the most performant options 😄 there are of course more subjective reasons you may opt for a library over another - you may be willing to sacrifice some microseconds for a DX/API you like more 😉
We'll also aim to expand to other types of benchmarking and comparison - I'm already investigating capturing error messages and traces, inspired by bsky.app/profile/null...
Proud to have teamed up with @eskimojo.bsky.social on Schema Benchmarks! 🙌
Valibot and Typia neck-and-neck on bundle size (~1.9KB gzipped)—the fight for the smallest bundles is heating up! 🔥
Transparent metrics like these help us all improve—dive in and let us know what you think!
To see our results in depth, check out schemabenchmarks.dev!
Reckon we've missed a library, or thought of an improvement to our methodology? We'd love to hear from you! github.com/open-circle/...
Want to do one better and DIY? Thanks! Give this a read: schemabenchmarks.dev/contributing
Now for parsing; where the schema returns a new value. We mark try/catch tests with *, and "abort early" tests with †.
Libraries that can abort early (Valibot, Effect, joi) have an advantage with invalid data, and Typebox clocks in slowest, constrasting its validation results.
Validation time! That's simply checking whether a value matches a schema, and only returning a boolean. We check against both valid and invalid data (these results are for invalid data):
Typia, Typebox and Ajv are all blazing fast at this. Yup is far slower, with joi following.
With regards to initialisation time:
Some libraries are very quick here (Typia, VineJS, Rod). Most libraries achieve a fairly speedy initialisation time, with the exception of Ajv - currently measuring in at over 4ms 😅
Our current results, starting with bundle size (compiled with @rolldown.rs):
Typia and Valibot lead here, with very similar results (~1.9KB minified + gzipped). Zod brings up the rear, maybe due to its extensive language support. Its mini variant however is far smaller, at 5KB.
Check out our welcome post over at schemabenchmarks.dev/blog/welcome!
We measure different aspects of runtime performance for schemas:
⏱️ Initialisation
✅ Validation
🔄 Parsing
We also translate 📦 bundle size directly into 🌩️download speed 😎
Incredibly hyped to announce Schema Benchmarks, a project I've been steadily working on in collaboration with @fabianhiller.com!
It aims to provide a central and transparent resource for many of the metrics that matter for schemas, including bundle size and runtime performance 😄
Should we drop a dedicated open-source project comparing ALL major schema libs? 🤔
We could test:
⏱️ Initialization speed
✅ Validation speed
⚡ Parsing speed
📦 Download time (bundle size)
If this gets traction… we launch it 🚀📊
getOrInsert is a util i end up ponyfilling in the vast majority of my projects, very much looking forward to it being supported enough to use natively
reported
the traditional way
Redux toolkit has pretty much nailed all the pain points I’ve previously had with redux, which I still use a ton and love, but wasn’t able to upgrade to rtk yet. Started redoing a very old app with it and it has so much clarity and way less boilerplate. Thank you @acemarke.dev, @phry.dev and all...
they're not attributes, they're properties - which also explains className and htmlFor:
developer.mozilla.org/en-US/docs/W...
developer.mozilla.org/en-US/docs/W...
The Apollo GraphQL VS Code extension now ships with Apollo Client Devtools!
This enables you to use the Apollo Client Devtools with React Native or node applications.
Try it out and let us know what you think 🙂
