-
Notifications
You must be signed in to change notification settings - Fork 36
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
Cannot read properties of undefined (reading 'sentry') when using reactComponentAnnotation with @react-three/fiber #530
Comments
Thanks for writing in. I forwarded this internally. I think @0Calories will take a look! |
Hi @Y0lk, thanks for reporting this, I reproduced this locally and confirmed the crash is caused by the plugin adding the
Would these settings be helpful in getting your project running with |
This would be really helpful |
I think this would be good additions, is there a way too to add to the error log the component/file name, so that it's easier to debug and add to these lists? |
Definatly, I had the problem today when using next.js, so I opened a ticket in the sentry-javascript repository (getsentry/sentry-javascript#13413), it is only now that I found this ticket, the suggested configuration options would for sure be helpful, especially as it would allow us to NOT set reactComponentAnnotation to false and completly disable the new feature |
Thank you for opening this up. I had a bad time debugging what caused issues in our codebase after integrating Sentry. Are there any updates yet? |
@jbednar97 no updates. As a workaround please disable |
Disabling the reactComponentAnnotation in the sentry config files works |
Environment
@sentry/webpack-plugin 2.16.1
Steps to Reproduce
Expected Result
It wouldn't be possible to annotate the @react-three/fiber components but it should at least not crash.
Actual Result
Crashes with the following error: Cannot read properties of undefined (reading 'sentry')
I imagine the reason why this happens is because of how @react-three/fiber works, where it turns JSX into THREE objects. reactComponentAnnotation is unusable in our project because of this issue so it'd be great if there was a way to fix this. At the very least, you might wanna add some kind of warning to your documentation.
The text was updated successfully, but these errors were encountered: