feat: prepare react 19 compatibility#2810
Open
noahwaldner wants to merge 5 commits into
Open
Conversation
🦋 Changeset detectedLatest commit: 019f33b The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for fondue-components ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for fondue-components ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
SamuelAlev
approved these changes
Jul 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Prepares the packages
components,iconsandtokensto be compatible with react 19Code changes for v19 compatibility
useRef()without argument → explicit initial value@types/react@19will make the argument required.RefObject<T> → RefObject<T | null>In react 19
useRef<T>(null)returnsRefObject<T | null>;parameters must accept it. Backward-compatible in v18.RefObject<T> → structural { current: T | null }Same nullability, but in return types/props the generic spelling fails react 18's covariance check, so the plain structural type is the only form valid under both.
- Duck-typed element narrowing →
isValidElement<Props>()react 19 changes
ReactElement's default props fromanytounknown, breaking.propsaccess after manual checks.JSX.Elementannotations →ReactElementreact 19 removes the global JSX namespace (now React.JSX / importable only).
react 19 deleted
ReactSVG; its replacementSVGElementTypein 18, and the type is publicly exported, so neither import works for both majors.forwardRefresultreact 19's
FunctionComponentlost its legacycontext?: anysecond parameter, so two-argument functions are no longer valid component types