5 ms·
We've been using Webpack for a number of years now with our massive webapp. A few months ago we started using esbuild for our development setups. Build times w
by emilsedgh 6y ago
We've been using Webpack for a number of years now with our massive webapp.
A few months ago we started using esbuild for our development setups. Build times went from ~6 minutes to ~1.
This is a sweet spot for us as esbuild is performing really well and made our development much easier. we still rely on webpack for our staging and production builds.
The reason for this is esbuild doesn't support a variety of production necessary features (transpiling to older ES, uploading bundles to S3, etc)
But I'm very happy with our "esbuild for development, webpack for deployments" process.
Any reason other people are not taking a similar approach?
- manigandham 6y ago> "uploading bundles to S3" Why are you using the bundler to do that?
- emilsedgh 6y agoBecause it could and it knows my assets the best. Im sure there are alternative methods but with Webpack it's been super easy.
- earthboundkid 6y agoESBuild will transpile to different versions of ES6. It won’t drop down to 5. I assert that you don’t need 5 support because you aren’t actually QAing IE11 and if you did, you’ll learn that it’s actually been broken and no one reported it.
- emilsedgh 6y agoThat may not be far from truth. Maybe I will have our people test IE11 and if it's not really working we'll drop it.