Reporting Issues

It's important that before submitting any issue that you have a thorough understanding of the Quick Start first. Even if you are an experienced ClojureScript developer this is required reading.

It's helpful, but not essential, to first check the existing bug reports, the mailing list, or the Freenode #clojurescript IRC channel and ensure that the issue hasn't been reported before.

Also, it can be helpful to ensure that you are running the latest released version of ClojureScript. Also, checking against ClojureScript master is prudent—frequently when bugs are found, fixes are quickly committed (see instructions below).

It is essential, however, to report the bug using ClojureScript only. Downstream tooling often interacts with the ClojureScript compiler in non-trivial ways, and the best way to isolate the issue to ClojureScript is to remove them from the report altogether.

cljsbuild

cljsbuild is a popular build tool in the ClojureScript community. Removing it from your issue reproducer is a simple matter.

Make a build.clj file using the same :compiler settings from your project.clj that is needed for your issue reproducer.

(require 'cljs.closure)

(cljs.closure/build "source-path"
  ;; relevant :compiler settings
  )

You can run this script without cljsbuild like so:

lein trampoline run -m clojure.main build.clj

The same approach may be taken for reproducers for REPL issues as demonstrated in the Quick Start.

Installing from master

Make a checkout of the ClojureScript repository. From the root of the project run the following:

./script/build

This will install ClojureScript into your local Maven. Make note of the version when it scrolls by. Use this in your project.clj or pom.xml. If you are using cljsbuild make sure to follow the cljsbuild build instructions above.