On Thursday, November 27, 2014 2:09:58 AM UTC+11, Matthew Gertner wrote: > My colleague was complaining about waiting ~20 seconds for his ClojureScript > to compile and discovered this post on Stack Overflow: > http://stackoverflow.com/questions/20917202/auto-building-clojurescript-files-for-compojure-app. > In a nutshell, compilation time goes _way_ down if `optimization` is set to > `:none`, but some hackery is needed to get the resulting JS to run. (I didn't > check yet whether `:none` is a supported value or whether any unsupported > value would have the same effect.) > > Is there some option for turning off optimization completely that we haven't > been able to find? If not, is there some reason not to support this? Wouldn't > it be possible to adapt the parser so that it emits runnable JS without any > optimization at all during the dev process? The compilation time speedup is > really significant.
If you want to mix `:none` with a unittest framework, then this may help: https://github.com/mike-thompson-day8/cljsbuild-none-test-seed -- Mike -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescript@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript.
