As well as being PLEASINGLY FASTER to an extent that is really difficult to overstate how nice it is… esbuild also has an uncomplicated, nicely documented API.
I’ve found it much easier to get specific things I want to happen by configuring esbuild than by configuring webpack and babel.
I wanted to use esbuild for a greenfield but I found I could not mock with jest. I’m sure things will change in the future but it was bad timing. I tried swc and ran into rough edges too. Just an unlucky moment in time + stack.
Julia has a great blog, another great post. I wonder if she is “sprinkling in” Vue. I always thought that was a neat trick of Vue, easy integration if you want, never tried it.
I had a breakthrough with webpack when I followed along in a Build Webpack from Scratch type post. I can’t find the link anywhere (sry). I reminds me of understanding git by mkdir/touch files. Pulls back the curtain. It’s complicated and webpack might not even be the defacto tool in the future. Idk.
Kinda baffled that they’re using esbuild because they don’t understand what the import syntax does. If they’re comfortable with script tags, why not use those with import syntax? It’s further confusing because Vue’s build tool, Vite, uses esbuild.
It’s pretty clear from the article that Julia doesn’t know about <script type="module"> (or didn’t anyway, I will imagine she has been emailed/Tweeted) by now. It reminds me of Dan Abrahmov’s Things I Don’t Know article. I’ve learned a lot from Julia’s zines about SQL, HTTP, Bash, etc. so it’s interesting to read a post where I definitely know (or knew) more than her. :-)
I don’t know what the import syntax does, either, but I’ve heard esbuild is fast, so I could easily imagine myself being in the same situation.