Esbuild – An extremely fast JavaScript bundler

Post by eyelidlessness » Fri, Oct 15, 2021, 12:06 AM UTC

spartanatreyu wrote: post #270

eyelidlessness wrote: post #219

Earlier quoted context omitted.

ESBuild’s author and docs[1] are quite clear about its future scope: > [… a list of features that are already done…] > After that point, I will consider esbuild to be relatively complete. I'm planning for esbuild to reach a mostly stable state and then stop accumulating more features. This will involve saying "no" to requests for adding major features to esbuild itself. I don't think esbuild should become an all-in-o…

"Weakness: since ESBuild doesn’t expose its AST, plugins are often slow which can undermine the benefits of the tool" I think by the time we even care about the performance of a plugin being "golang" fast, we will have rome built in rust. Rome will be the full kit and caboodle at native speeds (bundler, tree shaking compiler, linter, type checker, etc...), whereas esbuild will be the rome-lite for when you just want…

Post by kyawzazaw » Fri, Oct 15, 2021, 6:28 AM UTC

praveenperera wrote: post #180

maga wrote: post #110

Often overlooked things when discussing esbuild here: 1. It's not just a faster replacement for a single %tool_name% in your build chain: for the vast majority of cases, it's the whole "chain" in a single cli command if you're doing it right. That is, you don't just stick it inside, say, webpack as a faster replacement for babel (although you can). No, you look carefully through your webpack configs and its myriad of…

> 3. The most impressive part about esbuild development is not just that it's one guy writing it: it is the level of support and documentation he manages to provide alongside. And the one guy writing it is Evan Wallace, co-founder and CTO of Figma. I don't know how he has the time!

Post by ZephyrBlu » Fri, Oct 15, 2021, 7:09 AM UTC

kyawzazaw wrote: post #274

ZephyrBlu wrote: post #146

Earlier quoted context omitted.

So working a shit ton then.

No idea on Evan Wallace's perspective but there is a possibility that it isn't seen as work. It would like be me solving sudoku or some of my friends building LEGOs or solving extremely hard jigzaw puzzles

Post by exdsq » Fri, Oct 15, 2021, 2:23 PM UTC

phist_mcgee wrote: post #268

theptip wrote: post #264

Earlier quoted context omitted.

I take your point, but I think you could fairly say that JS has been going through growing pains since its inception 25 years ago. It's always been a fast-moving, inconsistently-implemented language. (E.g. Netscape / Mozilla vs. IE support for browser features). Maybe things are going to calm down a bit? I could believe it. But I just don't see the churn stopping. The browser-as-OS is going to keep getting new featur…

>when everybody starts using wasm I would say this is a far off possibility. The need to write WASM code rarely surfaces for the average SPA, and really seems like its more applicable to games or sites with heavy processing needs. For better or worse, it's going to be JS/TS for a long while yet.

Post by presentation » Fri, Oct 15, 2021, 2:59 PM UTC

alfonsodev wrote: post #235

crubier wrote: post #179

Earlier quoted context omitted.

SWC in NextJS is still in canary with experimental settings, but it took me 3 lines of code yesterday to make it work on a fairly large app ( https://labelflow.ai ). Hot reload times instantly went from 10s to 1s. Twitter discussion here https://twitter.com/vlecrubier/status/1448371633673187329?s=... Overall I’m pretty bullish on Rust tooling and integration within the JS/ Wasm ecosystem !

could you provide a link on how to enable this experimental setting ? thank you.

    experimental: {
        swcMinify: true,
        swcLoader: true
    }