-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
Add initial benchmark to compare against babel-loader based approach #13
Comments
The improvement in my project has been around 45 sec build time -> 6 sec build time in github actions, going from babel-loader to esbuild-loader |
@Nickhoyer That's impressive! |
I took minification benchmarks here: In a proprietary codebase I have access to, it reduces build-time by 2~3min (7m → 4m) by replacing babel-loader and Terser with esbuild. If you know of any large public codebases that transpiles using babel-loader and has a pretty minimal Webpack config, let me know and I can test there. I tried it on vue-hackernews-2.0 but the codebase is too small and was seeing only about a 1s difference (7s → 6s). We can also make an issue/PR to add a esbuild option to Vue CLI that uses this. |
Not related to babel, but my results for medium-sized project with bundle size of 6MB are:
|
In my case: babel-loader + thread-loader - 87s |
My nextjs project's build time went from 150s to 70s |
It would be cool to see the impact against babel-loader. I wonder if there's some open source project that could be used for figuring out the performance difference. Also pros/cons would be good to understand. At least we would lose any Babel plugins with esbuild but that's not a big deal for some projects.
The text was updated successfully, but these errors were encountered: