fix: prerender output paths should not include basename #14739
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.
Description
When using basename in react-router.config.ts, prerendered files are incorrectly output to a subfolder matching the basename (e.g., build/client/base/index.html instead of
build/client/index.html).
The basename is meant to define the deployment path prefix, not the build output directory structure. The prerender logic was using normalizedPath (which includes basename)
instead of the actual route path for determining output file locations.
Changes
Impact
No compatibility issues - This is a bug fix that corrects the output path behavior. Previously, prerendered files with basename would be placed in wrong directories, causing
404 errors when deployed.
Fixes #14587