Turbopack: Pages Router file named sitemap.js misclassified as App Router metadata route, breaks build with false getServerSideProps is not supported in app/ error - #97481
Closed
Arjunr7019 wants to merge 2 commits into
Conversation
…uter metadata route, breaks build with false getServerSideProps is not supported in app/ error #97436
Arjunr7019
changed the title
Arjunr7019
changed the title
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
1 participant
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.
What changed?
sitemap.jsfile was incorrectly classified as an App Router metadata route.getServerSideProps is not supported in app/error during the build.Why?
A
sitemap.jsfile in the Pages Router was being incorrectly identified as an App Router metadata route. This caused the build to fail with a misleadinggetServerSideProps is not supported in app/error.How?
Updated the route detection/classification logic so that
sitemap.jsfiles under the Pages Router are handled correctly and are not mistakenly treated as App Router metadata routes.Related Issue
Fixes #97436