refactor(flight): Centralise logic for generating module manifest keys #78517
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.
Unifies resource-key generation via a shared
getModuleResourceKey()
helper, so client, server, and edge compilers reference modules with the same canonical string (path + query + barrel suffix, normalised + relative).Removes bespoke key logic from the flight loader, client-entry, and manifest plugins; all delegate to the helper to avoid drift. The manifest now retains query strings for named module IDs (enabling userland "use client" virtual modules). This was used inconsistently before. Turbopack’s "use client" proxy also now includes
ctx.query_str
for parity.Also a drive-by fix to make sure
pluginState.edgeRscModules
is actually used for edge RSC mapping.