Currently boot-cljs-test adds dependency to doo directly using set-env!. This causes side-effects in case if cljs-test is being run as part of package task, the doo dependency would be added to resulting uberjar.
Simple workaround would be to add the dependency with :scope "test" but even then if would case side-effect on classpath.
Proper way would be to use pods to isolate this dependency.
Currently boot-cljs-test adds dependency to doo directly using
set-env!
. This causes side-effects in case if cljs-test is being run as part of package task, the doo dependency would be added to resulting uberjar.Simple workaround would be to add the dependency with
:scope "test"
but even then if would case side-effect on classpath.Proper way would be to use pods to isolate this dependency.