Package exports: resolve to real paths, fix module duplication in output #1198
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:
Fix: #1197
unstable_enablePackageExports
andunstable_enableSymlinks
in combination may result in non-real module paths in the graph, becausePackageExportsResolve
only usescontext.doesFileExist
and does not necessarily return real paths.Often, especially with pnpm, this results in a module appearing multiple times under different paths in the output bundle, as if duplicated on the file system, which causes incorrect behaviour for stateful modules and increases bundle size.
The fix mirrors the implementation of
resolveSourceFileForExt
in the non-exports resolver.Changelog:
Differential Revision: D52964393