-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Sentry Remix Causes Remix defer to fail in @remix-run/node@1.11.0 #6883
Comments
Hi, since the 1.11.0 Remix release is quite new we have to check for compatibility so stay tuned! We're tracking it here: #6888 |
Thanks for the quick response. Glad you guys are tracking this. Quick note on the nature of the issue: Here Sentry.init actually changes the behavior of Remix in a breaking way (I presume there is monkey patching or something involved). The issue is not that Remix 1.11.0 breaks Sentry, but rather Sentry breaks Remix 1.11.0. |
This might be the same issue that I opened on Remix earlier this week (remix-run/remix#5211). If so, it's not related to Sentry (my reproduction was not using Sentry at all). |
Related: #6888 |
I believe I am also running into this issue. Remix 1.15.0 |
I was able to reproduce the issue here: https://codesandbox.io/p/sandbox/pensive-lederberg-hq4i4k?file=%2Fapp%2Froot.tsx%3A20%2C14-20%2C20 |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which package are you using?
@sentry/angular
SDK Version
7.31.1
Framework Version
Remix 1.11.0
Link to Sentry event
No response
SDK Setup
No response
Steps to Reproduce
Use deferred data loading in Remix@1.11.0. The output shape when calling useLoaderData will be changed. (The data is under the "data" key instead of being the return value)
Expected Result
useLoaderData should return what was passed to defer
Actual Result
useLoaderData returns what was passed to defer wrapped in an object.
The text was updated successfully, but these errors were encountered: