Packages

react-hook-form

7.91.0 · 23 Oct 2026MIT42M / weekRepositoryHomepagenpmAtom feed

Upgrading react-hook-form from 6.0.0 to 6.15.8

65 releases in betweennotes for 20

Other targets from 6.0.0Latest7.91.0
1+
change to make
0
advisories fixed
12+
new
?
fixes

Counted from 20 of 65 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • breaking6.6.0

Release by release

  1. 6.14.1 – 6.15.811 releases, nothing new or fixed; 10 without a note

  2. 6.14.0

    31 Dec 20201 new
    • new

      New formState isValidating, this will set to true during validation.

  3. 6.12.1 – 6.13.14 releases, no release note

  4. 6.12.0

    28 Nov 20201 new
    • new

      New custom hook useController: This custom hook is what powers Controller, and shares the same props and methods as Controller. It's useful to create reusable Controlled input, while Controller is the flexible option to drop into your page or form.

  5. 6.10.1 – 6.11.57 releases, nothing new or fixed; 6 without a note

  6. 6.10.0

    31 Oct 20201 new
    • new

      Controller will have an extra ref props to improve DX in terms of focus management.

  7. 6.8.1 – 6.9.613 releases, nothing new or fixed; 11 without a note

  8. 6.8.0

    9 Sep 20202 new
    • new

      New formState isSubmitSuccessful to indicate successful submission

    • new

      setError now support focus on the actual input

24 other lines we could not sort, mostly version bumps

  • Radio input default selection will return null instead of empty string ''

    6.15.0

  • valueAsNumber with empty input will return NaN instead of 0

    6.15.0

  • setValue without shouldUnregister:false will no longer deep clone its value instead with shallow clone

    6.14.0

  • When invoking reset({ value }) value will be shallow clone value object which you have supplied instead of deepClone.

    6.12.0

  • defaultValues is required to measure isDirty, keep a single source of truth to avoid multiple issues raised around isDirty

    6.11.0

  • When watch with useFieldArray, fields object is no longer required as defaultValue

    6.11.0

  • resolver with group error object will no longer need with trigger to show and clear error. This minor version made hook form look at parent error node to detect if there is any group error to show and hide.

    6.10.0

  • With shouldUnregister set to false, empty Field Array will default as submission result.

    6.9.0

  • When input unmounts touched and dirtyFields will no longer get removed from formState (shouldUnregister: true).

    6.8.4

  • With shouldUnregister:false defaultValues data will be part of the submission data

    6.8.0