ts-reset
typescript-runtime-type-benchmarks
ts-reset | typescript-runtime-type-benchmarks | |
---|---|---|
20 | 33 | |
7,588 | 560 | |
0.8% | - | |
4.2 | 9.7 | |
about 2 months ago | about 17 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.
ts-reset
-
Unleashing the Power of TypeScript: Improving Standard Library Types
TypeScript's standard library contains over 1,000 instances of the any type. There are many opportunities to improve the developer experience when working with strictly typed code. One solution to avoid having to fix the standard library yourself is to use the ts-reset library. It is easy to use and only needs to be imported once in your project.
-
Why doesn't TypeScript properly type Object.keys?
You might like TS Reset: https://github.com/total-typescript/ts-reset, which fixes this particular problem. I don't personally find it to be a big issue though.
Regarding runtime type checking, if you were to write something that can handle the total space of possible TS types, you would end up with incredibly complex machinery. It would be hard to make it perform, both in terms of speed and bundle size, and it would be hard to predict. I think Zod or perhaps https://arktype.io/ which target a reasonable subset are the only way to go.
-
Javascript vs typescript
https://github.com/total-typescript/ts-reset <-- this fixes the `(string | undefined)[]` issue and a few other quirks. Obviously it's annoying to need a library to fix quirks, but better than nothing.
-
Books/resources to improve TypeScript knowledge
Dude is an actual TypeScript wizard, his ts-reset package is a must have when dealing with JSON. He was featured in the VS Code day streams to show off some introductory TypeScript concepts and my big takeaway from that stream was this VS Code extension. Just stick // ^? on the line after something and it shows the type of the line above. Amazing with Prisma.
-
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
Personally I quite like ts-reset to "fix" some of the std lib types - JSON.parse will now return unknown. It's then up to you to decide how you wish to parse that unknown (zod, runtypes, io-ts are all reasonable options here). Won't ever be done by TS itself, as generating runtime code is a non-goal for the project.
-
Free Next.js Boilerplate for ⚡️High-Performance⚡️ Enterprise Apps
🛠️ Extremely strict TypeScript - With ts-reset library for ultimate type safety
-
How to construct this tuple type?
Ok, answered it myself: it was a perfect use case for ts-reset: https://github.com/total-typescript/ts-reset
- A 'CSS reset' for TypeScript, improving types for common JavaScript API's
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?
zod - TypeScript-first schema validation with static type inference
napi-rs - A framework for building compiled Node.js add-ons in Rust via Node-API
ts-async-kit - the easiest API to deal with promises in Typescript. Currently, ↩️ Retrying 🏃♂️ looping & 😴 sleeping
garph - Fullstack GraphQL Framework for TypeScript
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.
Superforms - Superforms is a SvelteKit library that helps you with server-side validation and client-side display of forms.
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
sonner - An opinionated toast component for React.
Wren - The Wren Programming Language. Wren is a small, fast, class-based concurrent scripting language.
nuxt-scheduler - Create scheduled jobs with human readable time settings
Prisma - Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB