Describe the change
I'm mostly comparing vite and webpack. Vite calls buildEnd once when the server stops according to their docs and my observations, while for webpack buildEnd is strictly about the build process and when the bundling is completed in the dev mode buildEnd fires, even though the server is still active.
Honestly, I don't know what is the best solution here, maybe creating new serverStart/serverEnd hooks that will use buildEnd in vite, but e.g. shutdown (https://webpack.js.org/api/compiler-hooks/#shutdown) in webpack, or add a note in the docs, that buildEnd behaviour varies.
Just wanted to get an opinion on whether it's transparent to have a hook that works quite differently 😸
URLs
No response
Additional information
Describe the change
I'm mostly comparing vite and webpack. Vite calls
buildEndonce when the server stops according to their docs and my observations, while for webpackbuildEndis strictly about the build process and when the bundling is completed in the dev modebuildEndfires, even though the server is still active.Honestly, I don't know what is the best solution here, maybe creating new
serverStart/serverEndhooks that will usebuildEndin vite, but e.g.shutdown(https://webpack.js.org/api/compiler-hooks/#shutdown) in webpack, or add a note in the docs, thatbuildEndbehaviour varies.Just wanted to get an opinion on whether it's transparent to have a hook that works quite differently 😸
URLs
No response
Additional information