Fix false duplicate warning for sitemap with generateSitemaps #88029
+83
−36
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 does this change?
When
app/sitemap.tsusesgenerateSitemaps(), Next.js only generates/sitemap/[id].xmlroutes and does not generate a root/sitemap.xml.However, in
next dev, the app route matcher always reserved/sitemap.xmlfor
sitemap.ts, which caused a false duplicate route warning when usersdefined
app/sitemap.xml/route.tsfor a sitemap index.This PR updates the dev app route matcher to skip generating the single
sitemap.xmlroute for sitemap entries and adds a regression test.Why is this safe?
Reproduction
See issue #87314.