fix(swc): avoid treating Pages Router sitemap and robots routes as app entries - #96967
Open
RajeshKumar11 wants to merge 1 commit into
Open
fix(swc): avoid treating Pages Router sitemap and robots routes as app entries#96967RajeshKumar11 wants to merge 1 commit into
RajeshKumar11 wants to merge 1 commit into
Conversation
RajeshKumar11
force-pushed
the
fix/pages-sitemap-turbopack-build
branch
from
August 8, 2026 12:17
6e3680b to
d30a55a
Compare
RajeshKumar11
force-pushed
the
fix/pages-sitemap-turbopack-build
branch
from
August 8, 2026 12:19
d30a55a to
4a4c122
Compare
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?
Prevents the SWC
react_server_componentstransform from treating Pages Router routes namedsitemaporrobots(e.g.,pages/sitemap.js) as App Router metadata entries.Why?
When building a Pages Router site with Turbopack, pages named
pages/sitemap.jsorpages/robots.jsexportinggetStaticPropsorgetServerSidePropsfailed during build with"getStaticProps" is not supported in app/. The transform was matching these route names with a metadata regex without checking if the file actually resided insideapp_dir.How?
In
ReactServerComponentValidator::assert_invalid_api, updatedis_app_entryto verify thatself.filepathis located insideself.app_dirbefore treating metadata route names (sitemap,robots,manifest, etc.) as App Router entries. Added an e2e test coveringpages/sitemap.jswithgetStaticProps.Fixes #96859