feat: support import defer in module graph#640
Merged
bartlomieju merged 1 commit intomainfrom Apr 20, 2026
Merged
Conversation
Include `import defer` and `import.defer()` dependencies in the module graph instead of skipping them. Deferred imports need to be fetched and compiled (prepared) so the runtime can instantiate them, even though evaluation is deferred until first namespace access. Added `ImportDefer` variant to both `StaticDependencyKind` and `DynamicDependencyKind`. Deferred imports are treated as ES module imports for graph building purposes (same resolution mode and import kind as regular imports). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Include
import deferandimport.defer()dependencies in the module graph instead of skipping them.Previously, deferred imports were returned from (
return) in the dependency collector, meaning they were completely excluded from the module graph. This causedLoading unprepared moduleerrors at runtime because the deferred module was never fetched or compiled.Deferred imports need to be in the graph so they are fetched and compiled (prepared), even though evaluation is deferred until first namespace access at runtime.
Changes
ImportDefervariant toStaticDependencyKindandDynamicDependencyKindImportKind::Es, same resolution mode)Needed by denoland/deno#32360 (TC39 import defer proposal).
🤖 Generated with Claude Code