--- title: Form v2 is here: All you need to know about the alpha description: TanStack Form v2 alpha reworks the library's core APIs based on a year of v1 feedback. Validators and listeners move from an event-keyed object to a pipeline... canonical: https://daily.dev/posts/form-v2-is-here-all-you-need-to-know-about-the-alpha-jodiafcgr twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Form v2 is here: All you need to know about the alpha | daily.dev og:description: TanStack Form v2 alpha reworks the library's core APIs based on a year of v1 feedback. Validators and listeners move from an event-keyed object to a pipeline... og:url: https://daily.dev/posts/form-v2-is-here-all-you-need-to-know-about-the-alpha-jodiafcgr og:image: https://api.daily.dev/og/posts/joDiaFcgr.png og:image:alt: Form v2 is here: All you need to know about the alpha og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Form v2 is here: All you need to know about the alpha **[TanStack](https://daily.dev/sources/tanstack-blog)** · 10 min read · 0 upvotes · 0 comments ## Summary TanStack Form v2 alpha reworks the library's core APIs based on a year of v1 feedback. Validators and listeners move from an event-keyed object to a pipeline model where each entry declares its own triggers and optional 'when' conditions, eliminating duplicate validator registration and awkward workarounds for multi-trigger or multi-validator scenarios. New formOptions.strictSchema and formOptions.looseSchema modes let developers choose whether the schema or the default values drive type inference, addressing mismatches like a required Date field starting as null. Form composition now supports branded field components so mismatched inputs (e.g. NumberInput on a string field) throw type errors. SSR support is simplified: server validators live in shared formOpts, and serverValidate returns a typed result instead of throwing, removing the need for manual mergeForm/useTransform on the client. The alpha targets React first, with other adapters to follow, and a migration guide is available. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do TanStack Form v2 validators differ from v1's event-keyed validators? TanStack Form v2 replaces the event-keyed validators object with a pipeline array where each validator entry declares its own triggers, so one validator can run on both change and blur without being registered twice and without producing duplicate errors. Multiple validators can also share a trigger, with bailIfInvalid controlling whether one runs only if another passes. _Developers migrating forms to a new validation model can track TanStack Form updates like this on daily.dev._ ### What does formOptions.strictSchema do in TanStack Form v2? formOptions.strictSchema makes the validation schema the single source of truth for type inference instead of defaultValues, so a default value like appointment: null produces a type error if the schema requires a Date. This differs from the default mode, which infers types from defaultValues, and from looseSchema, which allows null or undefined defaults without erroring while still inferring the schema's stricter type elsewhere. _Teams choosing between schema-first and default-value-first typing can follow this kind of TanStack Form detail on daily.dev._ ### How does server-side form validation change between TanStack Form v1 and v2 for Next.js? In v2, the server validator moves into the shared formOpts so both client and server use the same configuration, and serverValidate returns a typed result object instead of throwing a ServerValidateError. The client passes the returned serverState directly to useForm, eliminating the manual useTransform and mergeForm steps v1 required to reconcile server and client state. _Developers wiring up SSR form validation can keep up with framework changes like this via daily.dev._ ## Similar posts on daily.dev - [Introducing TanStack Form – Frontend Masters Blog](https://daily.dev/posts/introducing-tanstack-form-frontend-masters-blog-tupv2md6r) · Frontend Masters · 0 upvotes · 0 comments - [A Guide to Modern React Form Architecture: TanStack Form \+ Zod \+ Shadcn](https://daily.dev/posts/a-guide-to-modern-react-form-architecture-tanstack-form-zod-shadcn-osvxw2xhz) · freeCodeCamp · 7 upvotes · 0 comments - [Getting Started with Angular Signal Forms](https://daily.dev/posts/getting-started-with-angular-signal-forms-rkhmrdrfv) · Telerik · 1 upvotes · 0 comments - [React-Admin: February 2026 Update](https://daily.dev/posts/react-admin-february-2026-update-frhm2auqr) · marmelab · 66 upvotes · 2 comments - [Building a signal-first form in Angular](https://daily.dev/posts/building-a-signal-first-form-in-angular-efbg2vvpj) · InfoWorld · 0 upvotes · 0 comments --- Tags: [#webdev](https://daily.dev/tags/webdev), [#react](https://daily.dev/tags/react), [#typescript](https://daily.dev/tags/typescript) [View this post on daily.dev](https://daily.dev/posts/form-v2-is-here-all-you-need-to-know-about-the-alpha-jodiafcgr) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Form v2 is here: All you need to know about the alpha","url":"https://daily.dev/posts/form-v2-is-here-all-you-need-to-know-about-the-alpha-jodiafcgr","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/form-v2-is-here-all-you-need-to-know-about-the-alpha-jodiafcgr"},"datePublished":"2026-08-23T12:20:50.785Z","dateModified":"2026-09-13T20:10:18.818Z","description":"TanStack Form v2 alpha reworks the library's core APIs based on a year of v1 feedback. Validators and listeners move from an event-keyed object to a pipeline...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/560c78955a98aa488c50f7f31a8c3c0e?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/560c78955a98aa488c50f7f31a8c3c0e?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"TanStack","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"TanStack","logo":"https://media.daily.dev/image/upload/s--TVIrvIT7--/f_auto,q_auto/v1787487634/logos/tanstack-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/tanstack-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/form-v2-is-here-all-you-need-to-know-about-the-alpha-jodiafcgr","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"webdev,react,typescript","timeRequired":"PT10M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"TanStack","item":"https://daily.dev/sources/tanstack-blog"},{"@type":"ListItem","position":3,"name":"Form v2 is here: All you need to know about the alpha"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/form-v2-is-here-all-you-need-to-know-about-the-alpha-jodiafcgr#faq","mainEntity":[{"@type":"Question","name":"How do TanStack Form v2 validators differ from v1's event-keyed validators?","acceptedAnswer":{"@type":"Answer","text":"TanStack Form v2 replaces the event-keyed validators object with a pipeline array where each validator entry declares its own triggers, so one validator can run on both change and blur without being registered twice and without producing duplicate errors. Multiple validators can also share a trigger, with bailIfInvalid controlling whether one runs only if another passes. Developers migrating forms to a new validation model can track TanStack Form updates like this on daily.dev."}},{"@type":"Question","name":"What does formOptions.strictSchema do in TanStack Form v2?","acceptedAnswer":{"@type":"Answer","text":"formOptions.strictSchema makes the validation schema the single source of truth for type inference instead of defaultValues, so a default value like appointment: null produces a type error if the schema requires a Date. This differs from the default mode, which infers types from defaultValues, and from looseSchema, which allows null or undefined defaults without erroring while still inferring the schema's stricter type elsewhere. Teams choosing between schema-first and default-value-first typing can follow this kind of TanStack Form detail on daily.dev."}},{"@type":"Question","name":"How does server-side form validation change between TanStack Form v1 and v2 for Next.js?","acceptedAnswer":{"@type":"Answer","text":"In v2, the server validator moves into the shared formOpts so both client and server use the same configuration, and serverValidate returns a typed result object instead of throwing a ServerValidateError. The client passes the returned serverState directly to useForm, eliminating the manual useTransform and mergeForm steps v1 required to reconcile server and client state. Developers wiring up SSR form validation can keep up with framework changes like this via daily.dev."}}]} ```