Split unstable_clientMiddleware
export into its own chunk
#12961
+58
−4
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.
Note, this PR is targeting the
brophdawg11/feat-middleware
branch.Luckily this turned out to be fairly straightforward. The route manifest now has
hasClientMiddleware
andclientMiddlewareModule
fields. It follows the same pattern asclientLoader
/clientAction
/HydrateFallback
where the manifest allows you to dynamically load theunstable_clientMiddleware
export if it's in its own chunk, otherwise you can fall back to loading it from the main route module. Note that this behaviour is also guarded behind thefuture.unstable_splitRouteModules
flag, so it might be a good idea to encourage turning this flag on when using client middleware given the performance implications.