Establishing Stable Module Identity Using Absolute Paths #24
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
same file so same absolute path cache works correctly resolving every module path to an absolute path before creating an asset, the bundler establishes a stable identity for each file in the dependency graph. Different relative import paths that reference the same file are normalized to a single absolute path, ensuring that the cache consistently returns the same asset instance. This prevents duplicate parsing, guarantees that each module receives a single unique ID, and allows all import edges in the graph to correctly point to the same node.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
same file so same absolute path
cache works correctly
resolving every module path to an absolute path before creating an asset, the bundler establishes a stable identity for each file in the dependency graph. Different relative import paths that reference the same file are normalized to a single absolute path, ensuring that the cache consistently returns the same asset instance. This prevents duplicate parsing, guarantees that each module receives a single unique ID, and allows all import edges in the graph to correctly point to the same node.