Zod finally has competition (...created by Zod?)

Summary

In this video, the creator dives deep into the evolution of TypeScript validation libraries, particularly Zod, and its limitations in performance and standardization. The introduction of a new standard schema reference, created by key contributors, unifies libraries like Zod, Valibot, and Archetype, enabling developers to seamlessly switch between validators without extra complexity. This standardization aims to simplify validation across various frameworks, such as TRPC and TanStack Forms. The video celebrates how this advancement will improve TypeScript development, offering better flexibility and performance for developers, while reducing the need for multiple validators in codebases.

Takeaways

• 😀 Zod has become a popular choice for TypeScript data validation, offering a powerful way to validate user input like strings and numbers.
• 😀 Despite its popularity, Zod has performance issues, particularly with TypeScript's type handling, and doesn't follow all validation standards.
• 😀 Colin, the creator of Zod, wanted to improve the ecosystem by introducing a standardized schema format that works with multiple libraries.
• 😀 The new standard schema reference allows developers to easily switch between different validation libraries, like Zod, Valybot, and Archetype, without changing application code.
• 😀 This schema reference helps solve issues of compatibility between libraries, reducing the need to manage multiple validation libraries in a project.
• 😀 The standardization of validation libraries is mainly aimed at library and framework authors, simplifying their work by supporting multiple validators through a single interface.
• 😀 The introduction of this schema format makes it easier for developers to move between different validation solutions, as they can now integrate multiple tools seamlessly.
• 😀 Not only does this provide more flexibility for developers, but it also addresses performance concerns by ensuring compatibility with other validators that may offer better performance.
• 😀 Key libraries and frameworks like TRPC, TanStack, and OpenO have already begun adopting the standard schema format, paving the way for future growth and compatibility.
• 😀 The standard schema format makes it simpler for developers to use any validator they prefer while maintaining correct types and avoiding integration issues.
• 😀 Ultimately, this change allows developers to future-proof their projects by easily switching validators as new and better tools emerge, without fear of breaking changes.

Q & A

What is Zod and how has it impacted the TypeScript ecosystem?

Zod is a validation library for TypeScript that gained popularity for its ability to validate TypeScript data structures. It allowed developers to validate inputs and ensure data integrity, covering a wide range of checks from string length to number ranges. Despite its benefits, it faced performance issues and did not fully comply with some validation standards.

What were the main limitations of Zod that were identified?

The main limitations of Zod included its relatively slow performance, poor TypeScript performance, and lack of adherence to certain validation standards. These drawbacks led Colin, one of the developers, to seek improvements to better align with validation best practices.

What significant change did Colin introduce to Zod and why?

Colin introduced the standard schema reference, which aimed to create a unified interface that could work across multiple libraries like Zod, Archetype, and ValleyBot. This was done to make it easier for developers to switch between different validation libraries without reworking their entire application code.

What is the benefit of the standard schema reference introduced by Colin?

The standard schema reference enables developers to define validation schemas once and use them across various libraries. This makes it possible to switch between validators like Zod, Archetype, and ValleyBot easily, without requiring adapters or significant code changes.

How does the standard schema impact developers using multiple validation libraries?

The standard schema allows developers to use multiple validation libraries in the same project seamlessly. For example, you can use Zod for deep validation on the backend and ValleyBot on the frontend without worrying about compatibility issues.

How does the new schema affect the use of validators across different frameworks?

With the new standard schema, frameworks and libraries can implement a unified validation interface. This means that validators from different libraries (like Zod, Archetype, and ValleyBot) can be used interchangeably across various frameworks without requiring custom adapters.

Why did Colin and other contributors focus on improving validation standards for the whole ecosystem?

Colin and other contributors wanted to improve the validation ecosystem not just for themselves but for the broader TypeScript community. By creating a standard schema, they made it easier for developers to switch between different validation libraries and ensured compatibility across frameworks and libraries.

What is the significance of the work done on Archetype and ValleyBot in relation to Zod?

Archetype and ValleyBot contributed to the development of the standard schema and focused on improving performance and modularity in validation libraries. These improvements help make validation more efficient and offer developers more options while ensuring that their libraries work together under the same standard.

What role does TypeScript performance play in the development of validation libraries like Zod?

TypeScript performance is crucial for validation libraries like Zod because poor performance can impact the overall user experience and scalability of applications. This is why the creators of these libraries, including Colin, worked on optimizing their performance and ensuring compatibility with TypeScript's type system.

How does the introduction of the standard schema benefit TypeScript developers in the future?

The introduction of the standard schema benefits TypeScript developers by providing a unified way to define and validate data across multiple libraries. As more libraries adopt this standard, developers will have more flexibility to choose the best validator for their needs without worrying about compatibility issues or needing custom integrations.