Fix custom client build.rollupOptions.output.entryFileNames
#13098
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.
Fixes #13091.
With the introduction of
future.unstable_splitRouteModules
, we added our ownbuild.rollupOptions.output.entryFileNames
config so that route chunk names would end up in the output (e.g.assets/route-client-loader-HASH.js
). This took precedence over any user provided config.This PR fixes this so any user-provided value for
build.rollupOptions.output.entryFileNames
takes precedence. It's worth calling out that our config is not required for the app to work, it's simply to make it easier to tell the chunks apart when debugging.