-
Notifications
You must be signed in to change notification settings - Fork 391
fix: handle ppr error message refactor #3499
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
Conversation
🦋 Changeset detectedLatest commit: b8dfcfa The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
Nice work @ceIia 🎉 and thank you for the contribution! |
bda8e2a
to
79cd87a
Compare
is there something i can do to fix the failing check @dimkl? i'm not 100% sure of why it broke |
79cd87a
to
69998a6
Compare
@ceIia we are facing an issue with the integration tests failing for a PR from a forked repo because the GH secrets are not shared. I will let you know about the progress in the next couple of hours. |
69998a6
to
4d3a5c1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes total sense to me. Thank you @ceIia
Description
in a pull request introduced last january in next.js (
dynamic-rendering.ts:153
), the message passed inReact.unstable_postpone
thrown for PPR bailout was changed, meaning the check implemented by #2518 was not enough anymore, and the bailout was not being rethrown anymore, breaking next.js builds using ppr, and probably other issues.i've updated it to match the latest version, but kept the old check for the sake of not causing a breaking change.
to test:
Checklist
npm test
runs as expected.npm run build
runs as expected.Type of change