3 ms·
It seems that swc is gaining more traction than esbuild, deno is using it, nextjs hired swc dev and rome is using swc too. Also one limitation by design of esb
by norman784 5y ago
It seems that swc is gaining more traction than esbuild, deno is using it, nextjs hired swc dev and rome is using swc too.
Also one limitation by design of esbuild is lack of customization, you cannot hook into esbuild and do your own things, but I read you could with swc.
But either way, both are way faster than the most popular ones.
- IggleSniggle 5y agoIt’s very easy to hook into esbuild. The simplicity and ease of integration is a big part of what I like about esbuild. I haven’t used swc, however, so I can’t comment on how it compares.
- dstaley 5y agoOne thing that's important to keep in mind is that esbuild is a bundler, in that it can take an input file that imports other JS files and create an optimized ready-for-production output bundle file. SWC cannot, yet, accomplish this.[1] It is in the works, however! But if I was choosing a replacement for Webpack to use today, I'd definitely go with esbuild. [1] https://swc.rs/docs/spack-basic/#mode https://swc.rs/docs/spack-basic/#mode