Skip to content

fix: keep incremental missing-module diagnostic location stable - #14947

Open
lazerg wants to merge 1 commit into
web-infra-dev:mainfrom
lazerg:fix/issue-14857-incremental-missing-module-location
Open

fix: keep incremental missing-module diagnostic location stable#14947
lazerg wants to merge 1 commit into
web-infra-dev:mainfrom
lazerg:fix/issue-14857-incremental-missing-module-location

Conversation

@lazerg

@lazerg lazerg commented Jul 25, 2026

Copy link
Copy Markdown

Summary

When a module imports the same missing request more than once, an incremental rebuild could report the "Module not found" error at a different import than a cold build. The incremental repair path groups the affected dependencies straight from a HashSet, so the dependency that supplies the diagnostic location was picked in arbitrary order. Sort each group back into the parent module's source order before factorizing, so the reported location stays the same whether the graph was repaired incrementally or built cold.

Related links

Closes #14857

Checklist

  • Tests updated (or not required).
  • Documentation updated (or not required).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: incremental missing-module diagnostics can point at a later use instead of the import

1 participant