Valibot v1.1 introduces new methods to simplify validation workflows: a message method for setting custom error messages across multiple schemas and actions at once, and a summarize method for pretty-printing validation errors into readable multi-line strings (inspired by Zod v4's prettifyError). It also adds getTitle, getDescription, and getMetadata for one-line metadata extraction, plus new parseJson and stringifyJson pipeline actions for handling JSON. The release also announces Motion and DigitalOcean as new partners, welcomes new contributors, and previews an upcoming Zod-to-Valibot codemod.
Table of contents
New partners and contributorsEasier custom error messagesSimpler error pretty-printingExtract metadata with one lineParse and stringify JSONThe future is bright!Questions this post answers
How do I set a custom error message for multiple Valibot schemas and actions at once?
Valibot v1.1 adds a message method that lets you wrap a pipe of schemas and actions with a single custom error message, replacing the need to repeat the same message on every action or use the config method. For example, v.message(v.pipe(v.string(), v.trim(), v.nonEmpty(), v.email(), v.maxLength(100)), 'The email is not in the required format.') applies one message across the whole pipeline. daily.dev surfaces library release notes like this for teams standardizing validation error handling.
How can I pretty-print Valibot validation errors into a readable string?
Valibot v1.1 introduces a summarize method that formats an array of validation issues into a human-readable, multi-line string showing each error message and its path, similar to Zod v4's prettifyError. This is intended for debugging and logging, turning raw issue objects into output like '× Invalid email: Received jane@example → at email'. developers debugging form validation errors can track new tooling like this via daily.dev.
Does Valibot support parsing and stringifying JSON directly in a validation pipeline?
Yes, Valibot v1.1 adds native parseJson and stringifyJson transformation actions that can be chained with other schemas and actions in a pipe. They automatically handle errors and edge cases, so a string can be parsed into JSON and then validated against an object schema in one pipeline, such as v.pipe(v.string(), v.parseJson(), v.object({...})). daily.dev helps developers evaluating schema libraries like Valibot keep up with new pipeline features.