fix: avoid builtStart during vite optimize #19356
Merged
+10
−0
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.
fix #19316
Description
Continuation from #19347. We started auto calling
builtStart
onresolveId
in Vite 6, so #19347 didn't have any effect.The PR is also disabling calling
buildStart
for the custom resolvers. This doesn't change anything, given that we only have two plugins (alias and resolve plugins) that don't have abuildStart
hook. Given that we also needs the resolve plugin during optimize, probably a good idea to force disabling autoStart for these too.I think we should deprecate
vite optimize
as we wanted and remove the newautoStart
param later on.