fix: not generate ssr route runtime module when client build #1087
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.
Summary
Generate route virtual modules based on
isSSR
in different build modes.Not generate ssr route runtime module when client build.
This avoids the SSR routing virtual module generated by client build from affecting the module number calculation of lazy compilation.
When ssr build, the client route runtime module still generated since some route match logic function need this structure.
Related Issue
web-infra-dev/rspack#5915
Checklist