Chris Truter

Otherwise, if you're set on pulling JS artifacts instead of source CLJS - maybe something dynamic and flexible like http://jspm.io would be a good fit

The principle of least surprise would probably be for boot-cljs-test to copy the resources to the runtime path also, but that cost may be prohibitive for some users. Cannot recall...

Have misspoken - the change needs to happen *inside* the `run-cljs-tests` task. Monkey-patching `add-node-modules!` is an option.. Will take a rough look at just cutting a SNAPSHOT that just handles...

Published two `0.3.1-hardlinks-SNAPSHOT` releases (confusingly the newer one uses symlinks), let me know if these resolve your issue.

Thanks for isolating the problem, the linking code is a bit naive about parent directories existing 🙂

Published another SNAPSHOT including 96a46cb5d8bbd417616d54f18269790f3ea54e35

Let me know how it goes with hard links. Perhaps the most flexible approach here would be lifecycle hooks where tasks can be attached?

Thanks for the repo, there are probably a few things at play here, and the chief root cause is that the karma server is out of process and therefore async...

Have published `0.3.1` with `update-fs?` fixed up Suggest fiddling with `wait` to get single runs working, and `watch` based workflows should be OK Definitely amenable to PRs 😍

Closing this ticket as it's gone cold - please reconnect if you're still having issues!