Remove experimental_ppr in next config - #101
Draft
hyoban wants to merge 1 commit into
Draft
Conversation
Owner
|
Hey thanks for the PR! I think it's a bit too early to remove this. This will create annoying warning for users who did not update to next 16 yet and for those who are already on 16 its not a big deal because it's unlikely they will want to export something with that name. |
hyoban
marked this pull request as draft
January 20, 2026 00:10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://nextjs.org/docs/app/api-reference/file-conventions/route-segment-config#version-history