Skip to content
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.

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

fix(optimizer): start optimizer after buildStart #12832

Merged
merged 1 commit into from Apr 11, 2023
Merged

Conversation

bluwy
Copy link
Member

@bluwy bluwy commented Apr 11, 2023

Description

Partial revert of #12593

As discussed, it's safer to init the optimizer after buildStart so that plugins are properly initialized before we start invoking the plugin hooks.

Additional context


What is the purpose of this pull request?

  • Bug fix
  • New Feature
  • Documentation update
  • Other

@stackblitz
Copy link

stackblitz bot commented Apr 11, 2023

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@patak-dev
Copy link
Member

Benchmark run for future reference, in case we would like to attempt moving the scanner/optimizer before the server starts again: https://github.com/vitejs/vite-benchmark/actions/runs/4668997365

@bluwy
Copy link
Member Author

bluwy commented Apr 11, 2023

Hmm the benchmark shows that this PR is better, so hey maybe that's a win 😄

@patak-dev
Copy link
Member

233ms better, wat. Could this be a flux @fi3ework? Anyways, hurray! 🥳

@patak-dev patak-dev merged commit cfe75ee into main Apr 11, 2023
12 checks passed
@patak-dev patak-dev deleted the optimizer-build-start branch April 11, 2023 15:48
@fi3ework
Copy link
Member

fi3ework commented Apr 11, 2023

233ms better, wat. Could this be a flux @fi3ework? Anyways, hurray! 🥳

I'm still thinking about how to make this "E2E" benchmark more stable without consuming too much CI resource and running time 🥹. This could be a flux 😅.

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.

None yet

3 participants