-
Notifications
You must be signed in to change notification settings - Fork 2.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
fix(v2_meta): hint data as being potentially undefined #6231
Conversation
🦋 Changeset detectedLatest commit: 2f658b7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 18 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 |
Note this is a duplicate of #5787. |
Good catch @aaronadamsCA, thank you! |
I think this PR is actually better than #5787... |
Reopening for @brophdawg11 consideration. |
yeah I like this one better too I think |
FWIW this should be a less common occurence now that #6107 is merged - it was a bug that we were still calling |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
I've been bitten by this in production a while ago, so here's my attempt at fixing it.
Not sure why we have duplicate types definitions in the react package, instead of a re-export from server-runtime.
Also, not sure this is the smartest fix, would definitely accept a better one
Closes: #6210
Testing Strategy: