Closed arichiardi closed 8 years ago
Ok a workaround is to have the doo
runner in some other source path, like so:
{:id "dev"
:source-paths ["src/cljs" "test/cljs"]
:figwheel {:on-jsload "launcher.test/run"
:css-dirs ["resources/public/styles"]}
:compiler {:main cljs-browser-repl.core
:output-to "resources/public/js/compiled/cljs-browser-repl.js"
:output-dir "resources/public/js/compiled/out"
:asset-path "js/compiled/out"
:optimizations :none
:source-map-timestamp true}}
{:id "test"
:source-paths ["src/cljs" "test/doo"] <<--- This is a different path
:compiler {:main 'launcher.runner
:output-to "resources/private/test/compiled/cljs-browser-repl.js"
:pretty-print false}}
Hi Andrea!
There are two possible questions here:
doo/run-tests
)?doo/run-tests
in your Figwheel build?Which one is it?
The error occurs because Figwheel doesn't have the [doo "0.1.6-SNAPSHOT"]
dependency, which is dynamically added by the plugin lein-doo
here.
The answer to number 2 is exactly my workaround...but there must be a better way. I am actually running my test inside the browser (printing the results to console) using a standard run that uses the standard run-tests. I don't think number 1 is that easy to achieve. But I have not explored the code.
If doo adds itself at runtime of course it cannot be seen by whoever is compiling code. This is not good for me and should be corrected, it should not interfere, aka it should be possible to have the two working at the same time..I will investigate anyways :)
Hi @arichiardi
After looking at this again I realize you could just solve it by adding [doo 0.1.6-SNAPSHOT]
to your list of dev dependencies, and things would properly compile. If you are still having trouble with this, can you try it out?
Otherwise, feel free to close this issue.
Yes it was long time ago and solved, thanks!
Hello @bensu and again thanks for this refactoring! First of all, my conf:
When I launch
lein figwheel dev
I receive a big:Any workaround?