TanStack Form for Next.js 16

Type-safe, performant forms with Server Actions and signal-based reactivity.

Agent Workflow (MANDATORY)

Before ANY implementation, use TeamCreate to spawn 3 agents:

1. •fuse-ai-pilot:explore-codebase - Analyze existing forms and validation patterns
2. •fuse-ai-pilot:research-expert - Verify latest TanStack Form docs via Context7/Exa
3. •mcp__context7__query-docs - Check form options and field API

After implementation, run fuse-ai-pilot:sniper for validation.

Overview

When to Use

• •Building forms with complex validation requirements
• •Need Server Actions integration for form submission
• •Implementing multi-step wizards or dynamic field arrays
• •Require real-time async validation (username availability)
• •Want type-safe forms with full TypeScript inference

Why TanStack Form

Critical Rules

1. •formOptions shared - Define once, use in client and server
2. •Server validation - DB checks in onServerValidate, not client
3. •Zod schemas - Client-side instant feedback
4. •useActionState - React 19 hook for Server Actions
5. •mergeForm - Combine server errors with client state
6. •SOLID paths - Forms in modules/[feature]/src/components/forms/

SOLID Architecture

Module Structure

Forms organized by feature module:

• •modules/auth/src/components/forms/ - Auth forms (login, signup)
• •modules/auth/src/interfaces/ - Form types and schemas
• •modules/auth/src/actions/ - Server Actions for form submission
• •modules/cores/lib/forms/ - Shared form utilities

File Organization

Key Concepts

Form Options Pattern

Define form configuration once, share between client and server. Ensures type safety and consistency.

Field API

Each field has state (value, errors, touched, validating) and handlers (handleChange, handleBlur).

Validation Levels

• •onChange - Real-time as user types
• •onBlur - When field loses focus
• •onSubmit - Before form submission
• •onServer - Server-side in action

Error Management

Errors exist at field-level and form-level. Use field.state.meta.errors for field errors, form.state.errorMap for form errors.

Reference Guide

Best Practices

1. •Define schemas first - Zod schemas drive both validation and types
2. •Shared formOptions - Single source of truth for client/server
3. •Debounce async validation - Use asyncDebounceMs for API calls
4. •form.Subscribe - Selective re-renders for submit state
5. •Field composition - Reusable field components with shadcn/ui
6. •Server errors merge - Use mergeForm to show server validation errors

Comparison vs React Hook Form