Run only what changed
Validate the active field, step, or group without rerunning unrelated rules or exposing errors for untouched inputs.
Your form changes one field at a time. Its validation should too.
Vest runs the rules that matter now, retains the truth established before, and makes stale async answers irrelevant.
npm i vestsuite.only('username').run(data)request #17 ignored / stale
previous field state preserved
THE RACE / 01
Three username checks race. Vest applies the current answer, ignores stale responses, and keeps the email result that did not run again.
Your suite contains the business rules. Vest manages how their truth changes over time: focused runs, retained results, pending work, and stale async responses.
A runtime for validation over time
A suite is a living validation result. It knows what ran, what can be retained, what is pending, and which result is still relevant.
Validate the active field, step, or group without rerunning unrelated rules or exposing errors for untouched inputs.
Vest merges each focused run into a living result, preserving trustworthy validation state from earlier interactions.
Track pending work, cancel obsolete requests, and prevent slow stale responses from replacing the current result.
Express linked fields, conditional sections, warnings, optional values, multi-step groups, and dynamic lists.
Run statelessly on the server, resume validation state in the browser, or share one suite across UI frameworks.
Keep business rules outside feature code in readable suites that are straightforward to unit-test and reuse.
Use Vest end to end, or bring another Standard Schema tool.
Use it as values change, async work overlaps, and steps unfold.
Ten practical tutorials move from a first suite to async state, typed schemas, and browser/server continuity.