Exception with cljsbuild once in windows about lein-cljsbuild HOT 4 CLOSED

Hey, are you using the exact (defproject ...) form from the tutorial that you linked? If not, please post your project.clj file.

I don't have a windows box to test against, so I might not be too much help. :(

The only time that I've seen errors deep in the com.google.javascript.jscomp stuff before was when a JAR was included in a project that conflicted with the Google Closure library. I think the offending library was closure-templates-clj. No idea if that problem has the same root as yours, though...

from lein-cljsbuild.

The OP raised this with me on some example code I've developed, two people have raised the same issue, both on Windows boxes.

https://github.com/djhworld/djhworld.github.com/issues/1
djhworld/testproject#1

Running the compiler on any *nix box or using Cygwin works fine.

I have a feeling this may be an issue with filepaths. Is there a step in the compiler where it copies the compiled JS to its destination?

from lein-cljsbuild.

hi emezeske..yes I've used the same code from the example... and now (I've upgrade my leinigen version to the latests) using :plugins [[lein-cljsbuild "0.0.14"]] ..neither work...In linux this work fine and I can run it well..but I don't know what happen with windows.....

from lein-cljsbuild.

@djhworld: The lein-cljsbuild plugin only copies files when you have the :crossovers feature enabled. With a simple configuration like that found in your blog post, lein-cljsbuild really shouldn't be doing much other than passing those options straight through to cljs.closure.build.

By default, the :compiler/:output-dir option is set to ".clojurescript-output". Would there be any problem creating a dotfile directory? It might be worth fiddling with that option.

It's quite possible that the ClojureScript compiler does copy files internally, but if that was a problem, one would assume it would not work at all under Windows (which I believe is not the case).

The only other thing I can think to suggest would be to try changing :optimizations from :simple to :whitespace. I have no idea if this will have an effect, but the stack trace does seem to be bubbling up from the heart of the optimizer, so it's worth trying to see if it makes any difference.

from lein-cljsbuild.