Skip to content

fix(module-runner): keep same import with different importer separately #20944

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −3
Draft

fix(module-runner): keep same import with different importer separately #20944

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions packages/vite/src/module-runner/runner.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -222,15 +222,16 @@ export class ModuleRunner {
url: string,
importer?: string,
): Promise<EvaluatedModuleNode> {
let cached = this.concurrentModuleNodePromises.get(url)
const key = `${url}:${importer}`
let cached = this.concurrentModuleNodePromises.get(key)
if (!cached) {
const cachedModule = this.evaluatedModules.getModuleByUrl(url)
cached = this.getModuleInformation(url, importer, cachedModule).finally(
() => {
this.concurrentModuleNodePromises.delete(url)
this.concurrentModuleNodePromises.delete(key)
},
)
this.concurrentModuleNodePromises.set(url, cached)
this.concurrentModuleNodePromises.set(key, cached)
} else {
this.debug?.('[module runner] using cached module info for', url)
}
Expand Down
Loading