Juho Teperi
Juho Teperi
If VIsualVM is writes to app standard input it would explain why it takes lost of CPU time. If not, it is just overhead from the debugger, but that seems...
Yeah, I've been thinking about this.
`:fail-fast?` is not `:report` option. It is top-level option like `:parallel`.
Oh. `:fail-fast?` is eftest option so I haven't included it in Boot task options, but even the extra options are passed into eftest.
I tried setting output-dir to Boot-cljs tmp-dir which I think would be the correct value, but didn't have success. The repl kept creating `out` dir. https://github.com/adzerk-oss/boot-cljs-repl/compare/repl-output-dir?expand=1 Also related #16, #22
First, cljs-repl `:port` option sets the Cljs Repl websocket server IP. This is separate to nREPL port. To change nrepl port you need to set `repl` task port option: ```...
Resource-root sounds good! We could also change the implementation a bit to be more similar to it: If I recall correctly current `asset-path` removes the path from start of the...
The problem with analyze path is that cljs sources are not necessarily in one path. But we can create a tmpdir to which we copy all the cljs files (and...
If I remember correctly, boot-cljs, copies all files in fileset to one directory before the build. So this would be easier to implement once boot-cljs-repl has been merged into boot-cljs.
Figwheel supports this so this might be solved if we leverage figwheel's client code.