@pandeiro: Yeah boot-cljs uses ns-tracker

https://github.com/boot-clj/boot/issues/282

I've been thinking that one solution would be to have convention for tasks which add dependencies for pods

Something like boot cljs --download-deps test --download-deps

what about the convention that tasks have a no-op mode, so they can download their deps dynamically still

that would i think solve the problem you encountered in every case

static dependency spec wouldn't work for every case because the deps could depend on other tasks or things like that

like a task could compute its dependencies dynamically

Yeah no-op would be effectively same as download-deps option

i think tasks should generally resolve their dependencies in the outermost layer

like where you create task state

usually you make the pod future there

the actual work happens in the inner middleware layer