-
Notifications
You must be signed in to change notification settings - Fork 92
fix: support ppr shells for dynamic page routes #3092
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
📊 Package size report 0.04%↑
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
@@ -356,7 +359,7 @@ export class PluginContext { | |||
// - `string` - when user use pages router with `fallback: true`, and then it's html file path | |||
// - `null` - when user use pages router with `fallback: 'block'` or app router with `export const dynamicParams = true` | |||
// - `false` - when user use pages router with `fallback: false` or app router with `export const dynamicParams = false` | |||
if (typeof meta.fallback === 'string') { | |||
if (typeof meta.fallback === 'string' && meta.renderingMode !== 'PARTIALLY_STATIC') { |
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.
Here's the fix for deploy failures -we tried to treat PPR shells as pages router fallbacks so we later on tried to read contents from server/pages
that was leading to ENOENT errors).
The other changes in this PR are to actually support those shells being uploaded to cache and used later on (instead of generating them on-demand later on again in runtime)
Description
We've been treating shells for dynamic ppr page routes as fallbacks for pages router and failing to assemble cache content to upload because of that.
This PR:
Tests
Adjusted PPR fixture to use dynamic page routes and added some assertions making sure thing do work
Relevant links (GitHub issues, etc.) or a picture of cute animal
Fixes #3073
Fixes FRB-1784