ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
Learn how to define requirements, create the smallest viable ClojureScript build with :advanced optimizations and externs, enforce trust boundaries, run operational checks, anticipate failure modes, and know when to adjust the design.
I'm planning a ClojureScript and shadow-cljs version bump on a project and want a documented recovery path in case the upgrade fails or is interrupted mid-build, leaving partially compiled output behind. From what I understand, several layers of cached artifacts exist: the compiler's :output-dir contents, shadow-cljs's .shadow-cljs/cache , the .cpcache from
A small frontend application is being considered for incremental migration from plain JavaScript to ClojureScript with no downtime. The goal is to mount ClojureScript components into isolated DOM nodes and routes while the existing JavaScript remains active, using feature flags and separate asset loading. ClojureScript compiles to plain JavaScript and can be
Migration setup I am migrating a small ClojureScript frontend (a handful of namespaces, Reagent UI) from an older build setup to shadow-cljs, with the goal of zero downtime for users. The dev side is fine: the watch build with :none optimizations recompiles changed namespaces and the page updates without a restart. The failure condition The problem appears o
clojurescript