4 ms·
Unless I'm misunderstanding the ClojureScript team posts, one of the motivations for tight webpack integration is that not every npm module is compatible with a
by piercebot 6y ago
Unless I'm misunderstanding the ClojureScript team posts, one of the motivations for tight webpack integration is that not every npm module is compatible with advanced compilation.
From the article[0]:
> But after nearly three years since we first shipped Node module processing via Closure, it’s apparent that too few of the most popular libraries can be subjected to advanced optimizations. While we still believe there’s promise here, the ClojureScript community will have to show the rest of the world the way by developing compelling JavaScript libraries that can be readily consumed by popular JavaScript tools, yet still be subjected to Closure’s phenomenal tree shaking and code splitting when building with ClojureScript.
0: https://clojurescript.org/news/2020-04-24-bundle-target https://clojurescript.org/news/2020-04-24-bundle-target
- christophilus 6y agoIs this likely? Clojurescript comes with a pretty big base bundle size due to the runtime, right? Like hello world is still over 100kb or something before gzip, right? (On my phone, so it’s hard to google the exact number.)
- john-shaffer 6y agoThat was a bug. It was fixed with this release, and swannodette added a test to ensure the size stays under 10k bytes: https://github.com/clojure/clojurescript/commit/5d64c2a142e5b41a4e4390f563d4412502704e23 https://github.com/clojure/clojurescript/commit/5d64c2a142e5...
- christophilus 6y agoSwank! That’s a massive improvement. I’m going to spin up a Preact project and see how it fares.