lein-cljsbuild vs shadow-cljs which is better?

lein-cljsbuild is simpler and integrates directly with Leiningen, ideal for existing Leiningen projects. Shadow-cljs offers more features like npm integration and superior hot-reloading, making it better for modern frontend workflows with JavaScript dependencies.

How to set up automatic compilation with lein-cljsbuild?

Use the 'lein cljsbuild auto' command after configuring source paths in project.clj. It watches for file changes and recompiles automatically, avoiding JVM startup delays for faster development cycles.

Does lein-cljsbuild work with the latest ClojureScript?

It has version constraints; the README notes that ClojureScript >=1.7.170 requires lein-cljsbuild >=1.1.1. However, due to limited updates, compatibility with newer versions might be untested or broken.

How to fix uberjar build errors in lein-cljsbuild?

The README mentions a known issue (#366) with hooks; instead of using hooks, configure :prep-tasks like ["compile" ["cljsbuild" "once"]] in project.clj to avoid failures during uberjar packaging.

What are the alternatives to lein-cljsbuild for ClojureScript?

Common alternatives include shadow-cljs for advanced features and npm integration, Figwheel Main for live reloading, or using the ClojureScript compiler directly with tools like deps.edn for more control.

How to launch a REPL with lein-cljsbuild?

Refer to the REPL documentation linked in the README, which provides various methods such as using 'lein cljsbuild repl-launch' or integrating with existing REPL tools for interactive development sessions.

Open-Awesome

lein-cljsbuild

NOASSERTIONClojure1.1.8

A Leiningen plugin for automatic ClojureScript compilation and development workflows.

GitHub

1.1k stars149 forks0 contributors

What is lein-cljsbuild?

lein-cljsbuild is a Leiningen plugin that automates the compilation of ClojureScript code into JavaScript. It solves the problem of manual compilation and JVM startup delays by providing automatic rebuilding on file changes and integrating compiler configuration directly into the Leiningen project file.

Target Audience

Clojure and ClojureScript developers using Leiningen as their build tool, particularly those working on web applications or libraries who need efficient compilation workflows.

Value Proposition

Developers choose lein-cljsbuild for its tight integration with Leiningen, eliminating the need for external build tools, and its features like parallel builds, REPL support, and testing automation that streamline ClojureScript development.

Overview

Leiningen plugin to make ClojureScript development easy.

Use Cases

Best For

Automating ClojureScript compilation during development
Configuring ClojureScript compiler options within Leiningen projects
Running multiple ClojureScript build configurations in parallel
Launching ClojureScript REPLs for interactive coding
Integrating ClojureScript testing into Leiningen workflows
Library development requiring compilation at different optimization levels

Not Ideal For

Projects not using Leiningen as their build tool (e.g., those based on Boot or tools.deps)
Teams requiring modern JavaScript toolchain integration like Webpack, Vite, or npm module bundling
Applications needing advanced hot-reloading or Hot Module Replacement (HMR) beyond basic file watching

Pros & Cons

Pros

Seamless Leiningen Integration

Configures ClojureScript compiler options directly in project.clj, eliminating the need for external build scripts and making development feel native to the Leiningen ecosystem.

Efficient Auto-Compilation

Watches source files and recompiles on changes with 'lein cljsbuild auto', avoiding repeated JVM startup overhead for faster iterative development, as highlighted in the README.

Parallel Build Support

Supports compiling multiple configurations simultaneously, useful for library development or different optimization levels, demonstrated in the advanced example projects.

Built-in REPL and Testing

Launches ClojureScript REPLs for interactive coding and runs external test processes, with dedicated documentation linked for seamless integration into workflows.

Cons

Hook Conflicts and Bugs

Known issues with hooks, especially for uberjar builds (issue #366), require workarounds like using :prep-tasks instead, adding complexity and potential for errors.

Ecosystem Lock-in

Tied strictly to Leiningen, making it incompatible with alternative Clojure build tools like Boot or tools.deps, which limits flexibility in modern Clojure projects.

Limited Active Maintenance

The latest version is 1.1.8 from years ago, with deprecation notes for features like crossovers, suggesting reduced updates and potential compatibility issues with newer ClojureScript versions.

Frequently Asked Questions

Related Projects

lein-figwheel

Figwheel builds your ClojureScript code and hot loads it into the browser as you are coding!

Stars2,875

Forks205

Last commit2 years ago

shadow-cljs

ClojureScript compilation made easy

Stars2,391

Forks187

Last commit5 days ago

Lumo

Fast, cross-platform, standalone ClojureScript environment

Stars1,875

Forks83

Last commit4 years ago

Devcards

Devcards aims to provide a visual REPL experience for ClojureScript

Stars1,535

Forks107