@hookform/resolvers breaking changes

7.0.0

6 breaking changes, first published November 3, 2026.

• Removed TypeCompiler.Compile
  TypeCompiler.Compile is gone. Import Compile from typebox/compile instead. github.com
• Behavior changed
  TypeBox's single required error is now one error per missing field, localized through the active TypeBox locale. Code that expects a single required error must handle several. github.com
• Behavior changed
  Error type values are now keyword names such as minLength instead of numeric ValueErrorType codes. Code that compares error types must be updated. github.com
• Behavior changed
  Validation error messages use TypeBox 1.x wording, so code that matches on message text may need updating. github.com
• Configuration changed
  The typebox resolver requires typebox ^1.0.0 as a peer dependency instead of @sinclair/typebox. Install typebox 1.x and remove @sinclair/typebox. github.com
• Signature changed typebox:typeboxResolver
  Was function typeboxResolver<Schema extends TObject, Context>(schema: Schema | TypeCheck<Schema>): Resolver<Static<Schema>, Context, StaticDecode<Schema>>; now function typeboxResolver<Schema extends TObject, Context, TypeContext extends... npmjs.com

6.0.0

4 breaking changes, first published October 19, 2026.

• Removed
  The effect-ts resolver now requires effect@^4.0.0 and no longer supports Effect v3. Schemas must be migrated to the Effect v4 Schema API. github.com
• Behavior changed
  Error type values change, for example Type becomes InvalidType and Missing becomes MissingKey. Code that matches on the old type strings must be updated. github.com
• Behavior changed
  Default error messages change text, for example 'is missing' becomes 'Missing key', and the received value is no longer included. Code that matches on these messages must be updated. github.com
• Signature changed effect-ts:effectTsResolver
  Was function effectTsResolver<Input extends FieldValues, Context, Output>(schema: Schema.Schema<Output, Input>, schemaOptions: ParseOptions | undefined, resolverOptions: {mode?: 'async' | 'sync'; raw: true;}): Resolver<Input, Context... npmjs.com

Check your code

These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.