fix(hydration): use useId
for dom variant
#325
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Next.js (and other SSR frameworks) frequently logs warnings about mismatched
id
attributes between the server and client.To address this issue, the React team introduced the
useId
hook, specifically designed to prevent such mismatches.Breaking Changes
Since
useId
was introduced in React 18, I updated the peer dependency to require React 18 or newer. Given that React 18 was released over two years ago, it seems reasonable for this library's new version to discontinue support for older React versions.Checklist