-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting Typescript errors when upgrading to React 18 #4904
Comments
Hey thanks for reporting. We’re currently busy working on the new major version, #4882 but we’ll get to this afterwards! |
Thanks @AbhiPrasad. In case anyone else runs into this, the quickest fix for now is probably to ignore the error (I had trouble with module augmentation, I think because ErrorBoundaryProps is not exported?). It should allow your build to proceed but you'll want to comeback and remove it once this issue is resolved:
|
I have opened #4966 to fix this issue |
We are resolving this with our next patch (version 6.19.7) so keep an eye out for updates and remember to remove your Thanks @cameronaziz for the initiative! Update: The patch is out https://github.com/getsentry/sentry-javascript/releases/tag/6.19.7 |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which package are you using?
@sentry/react
SDK Version
6.19.6
Framework Version
6.19.6
Link to Sentry event
No response
Steps to Reproduce
Hi, I've started getting the following Typescript errors in my build. It seems it has to do with
ErrorBoundaryProps
not having achildren
property declared. Addingchildren: React.ReactNode
to ErrorBoundaryProps fixed the issue for me.DefinitelyTyped/DefinitelyTyped#46691
Expected Result
Typescript errors should not occur when React.ErrorBoundary has children
Actual Result
The text was updated successfully, but these errors were encountered: