ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Shrink your ClojureScript bundle by enabling :advanced compiler optimizations and adding proper externs for external libraries like lodash. Follow a concrete example, verify runtime integrity, and understand the trade‑offs.
Learn how to shrink your ClojureScript bundle with Shadow CLJS’s :advanced compiler mode. A step‑by‑step guide covers config, externs, pitfalls, and verification to keep your production build fast and reliable.
Advanced Closure Compiler builds shrink ClojureScript bundles but risk breaking external libs. This guide shows how to enable :advanced, declare externs, export symbols, and verify the output for a robust production build.
I am configuring a ClojureScript build that compiles with :optimizations :advanced via the Google Closure Compiler. The goal is a minified production bundle where calls into a plain JavaScript library — accessed through the js/ prefix and goog.object — still resolve correctly at runtime. The constraint I am unsure about is the externs boundary. My understand
Moving a ClojureScript project from `:optimizations :none` to `:optimizations :advanced` triggers Google Closure Compiler property renaming. The goal is to preserve JavaScript interop property names across that compilation boundary without breaking external references. The uncertainty lies in version-sensitive externs handling: the bundled Closure Compiler v
clojurescript