true-myth
typescript-runtime-type-benchmarks
Our great sponsors
true-myth | typescript-runtime-type-benchmarks | |
---|---|---|
1 | 33 | |
852 | 546 | |
4.0% | - | |
9.1 | 9.8 | |
7 days ago | about 23 hours ago | |
TypeScript | TypeScript | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
true-myth
-
Unlocking type-safety superpowers in Typescript with nominal and refinement types
TS doesn't do anything at runtime no, but there are some type checking libraries that could help you. I don't know what packages you're talking about in particular, but if they are IO related you can try io-ts. More generally you could also look into true-myth for Maybe types and wrap any values that come out of your packages before allowing them to be passed into your code.
typescript-runtime-type-benchmarks
-
TypeScript please give us types
Has been heavily optimized, both in terms of its types and runtime performance. Even including the static parser, many types are about an order of magnitude more efficient than equivalent Zod. Early results show it as marginally faster than any validator currently published to typescript-runtime-type-benchmarks, not including more complex cases where (2) would give ArkType a much more significant advantage.
-
What are some of the best libraries you cannot work without?
Zod is a bit of an underdog but it is not fast, AJV which is slightly more common can validate and generate types too but requires using JSON syntax, TypeBox offers familiar syntax to Zod while still being JSON syntax in the background.
-
[AskTS] What do you think will be the future of runtime type checking?
First, they're not fast (runtime type checking benchmarks).
-
Typescript really hits the middle ground between extremely rigid statically typed languages on one extreme and no types at all dynamic languages on another extreme. Best type system
Aha, so you're using a library in Java for this. You know about libraries in TS for this, there are plenty of them btw, but you don't use them because it's so easy. Express has `any` type for `req.body` because authors don't care about this either and it's so easy. And TypeScript is the one to blame in that you prefer to work with `any` type for incoming data rather than validating it.
-
TypeBox: Runtime Type System Built on Industry Standards
It is so much faster than Zod that Zod basically doesn't show, https://moltar.github.io/typescript-runtime-type-benchmarks/ and according to bundlejs, https://bundlejs.com/?q=zod%2Czod%2C%40sinclair%2Ftypebox&treeshake=%5B*%5D%2C%5B%7B+default+%7D%5D%2C%5B*%5D&config=%7B%22analysis%22%3Atrue%7D, it is even smaller. I genuinely have no clue why Zod is this popular in 2023.
- What’s your favourite validation library?
-
TypeBox: Template Literals + Conditional Types at Runtime
TypeBox is a bit different to other libraries in this space where it's mostly intended to be used with a auxiliary JSON Schema validator. Although it provides a built in JSON Schema compiler (which is currently the fastest (not-AOT) runtime validator available for JavaScript today), it's equally intended to be used with validators like Ajv (or any other standards compliant validator)
-
Introducing ArkType: The first isomorphic type system for TS/JS
I do plan to add some direct comparisons to https://github.com/moltar/typescript-runtime-type-benchmarks as well but haven't had a chance yet.
-
Is using zod as the primary source of truth for Typescript types sensible/sustainable?
I think it's more of a case of the extremely low performance bar that's been set by the status quo (for even the simplest of validation structures). There's been a lot of focus on the TS type inference, and less on the runtime performance (which actually matters more as it does reduce operational costs). It probably wouldn't be such an issue if the performance was reasonable, but I mean here's the full breakdown https://moltar.github.io/typescript-runtime-type-benchmarks/.
-
Best schema validator for intellisense performance?
I found a benchmark for runtime performance, but I haven't found any for intellisense/editor performance.
What are some alternatives?
rxjs-ninja - RxJS Operators for handling Observable strings, numbers, booleans and more
napi-rs - A framework for building compiled Node.js add-ons in Rust via Node-API
complish - Generate auto-completion for any CLI via ChatGPT.
zod - TypeScript-first schema validation with static type inference
persisted-requests - [Beta] Ensure client REST requests are not lost in event of catastrophic failure / early program termination. Demo is in the link.
MikroORM - TypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Supports MongoDB, MySQL, MariaDB, MS SQL Server, PostgreSQL and SQLite/libSQL databases.
type-fest - A collection of essential TypeScript types
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
DreamCompose - A simple and easy-to-use framework for developing web application interfaces and websites. Create attractive user interfaces easily and intuitively.
Wren - The Wren Programming Language. Wren is a small, fast, class-based concurrent scripting language.
Prisma - Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB