Skip to content

Commit fcaf749

Browse files
anyesubluwy
authored andcommitted
fix(optimizer): define crawlDeps after scanProcessing and optimizationResult are complete (fix #14284) (#14285)
1 parent 40e99a1 commit fcaf749

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

packages/vite/src/node/optimizer/optimizer.ts

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -619,8 +619,6 @@ async function createDepsOptimizer(
619619
return
620620
}
621621

622-
const crawlDeps = Object.keys(metadata.discovered)
623-
624622
// Await for the scan+optimize step running in the background
625623
// It normally should be over by the time crawling of user code ended
626624
await depsOptimizer.scanProcessing
@@ -630,6 +628,7 @@ async function createDepsOptimizer(
630628
optimizationResult = undefined
631629
currentlyProcessing = false
632630

631+
const crawlDeps = Object.keys(metadata.discovered)
633632
const scanDeps = Object.keys(result.metadata.optimized)
634633

635634
if (scanDeps.length === 0 && crawlDeps.length === 0) {
@@ -680,6 +679,7 @@ async function createDepsOptimizer(
680679
runOptimizer(result)
681680
}
682681
} else {
682+
const crawlDeps = Object.keys(metadata.discovered)
683683
currentlyProcessing = false
684684

685685
if (crawlDeps.length === 0) {

0 commit comments

Comments
 (0)