@xiongtx java task will compile whatever java sourcefiles it finds in the fileset with the input roles - namely files in :source-paths and :resource-paths

@freakinruben you need to commit! the fileset after changing it and then return from a with-pre-wrap handler so that the following tasks can work with a changed fileset. sift is the task that does exactly that if you compose it properly, e.g.:

(comp (do-something) (sift ...) (do-with-moved-files))

@dm3 I saw that (target) (which is called after sift) commits, is it still required to commit! in my own task too? Because the task thats called after moving (compile clj) needs the original inputfiles and not the moved fileset..

(deftask move ...)
(deftask a (comp (cljs) (move)))
(deftask b (comp (system) (repl)))
(deftask c (comp (a) (b)))

@freakinruben not sure if you’ve read this part of the wiki: https://github.com/boot-clj/boot/wiki/Filesets#the-task-model. The fileset is a snapshot of your files that every task receives from the task before it and returns to the next task in the chain. It’s effectively an immutable value.

if you want to “modify” a fileset, you need to commit, otherwise your changes will not be seen by the other tasks

Hello All - I’ve tried a quick Google, but to no avail… I have an nrepl running on 127.0.0.1:5601 - how would I use boot to launch a command line REPL to connect to that nrepl..?

boot repl -c -p $PORT I think… In general boot has good help for every task with boot $TASK -h

is it possible for a boot script to run another boot script in the same JVM instance?

@sekao would (load-file "foo.boot") work?

@dave didn't think to try that, thanks!

the only thing i could see potentially being an issue with that is that if the script you're loading has (set-env! :dependencies '[[ .... ]]), it might have some weird effect on the dependencies

merge-env! can solve that

what's the idiomatic way to ensure that a dependency added only for when $DEV=true, so the lib is not added to the production CLJS bundle ?

should I use (merge-env! :dependencies ,,, etc.]) and do it in my dev-env task?

but then the Clojurescript code that tries to require it will throw an exception

I can't just leave it there and hope that cljs compiler's dead-code elimination would remove it and won't bundle for prod, since the check happens at runtime

@ag which check happens at run time?

there isn't something like lein profiles in boot, right?

so I'm struggling to find a way to have different cljs dependencies for dev and prod builds

for example if I have a dependency let's say [binaryage/devtools "0.9.4"], and I want this thing only be included to dev build (e.g. for when $DEV=true. How do I do that?

I can probably use a task like this:

(deftask dev-env  []
  (merge-env! :dependencies '[[binaryage/devtools "0.9.4"]])
  (environ :env ,,, ; etc

I guess the only viable way to solve this is by using different edn files and different cljs ids, amright?

(def deps
  (case (.toLowerCase (System/getenv "DEPLOY_ENV"))
    "prod" prod-deps
    "dev" dev-deps
    dev-deps))

(set-env! :dependencies deps)

then to ensure your prod build doesn’t throw exceptions… test locally 😄

can someone point to an example with multiple "profiles"/edn files? I think I almost got it. Having trouble with the correct naming of things

one thing I can't figure out when using (cljs :ids #{"js/dev"}) with js/dev.cljs.edn, how to ensure that it ends up compiling to main.js and not dev.js?

also I feel that compiler-options not being picked up when put in .edn file. seems :verbose true for example is being ignored (when it's in edn), but works when passed into the cljs task directly

@ag An easy way to do it is to have env/dev/src/main.cljs.edn and env/prod/src/main.cljs.edn, and include the former in your dev task and the latter in your build task

sigh... multiple builds with boot-cljs seems not straightforward to get. so is :output-to and :output-dir of compiler-options are ignored and precise path+filename is fully determined by the edn file?

that's so awfully inconvenient

what's :unified-mode ?

goddamit... can't make it work. so there's no way to force compiled cljs files to be in the right place, i.e. force it to respect :output-dir or/and :output-to ?

It will just output to the same location that it is found in src

src/main.cljs.edn => target/main.js

If you are serving resources from the classpath, your HTML should be able to include a <script src="main.js"></script> and it will just work

So what I was telling you above is, you would not have any src/main.cljs.edn, but instead would put different ones in env/dev/src/main.cljs.edn and env/prod/src/main.cljs.edn, for example, and make sure the right source-paths are included for each task

The env/dev/... one could point to a namespace like myapp.core-dev, which would call your myapp.core/init, but also bring in things like binaryage/cljs-devtools, additional logging, etc

Does that make sense @ag?

It does... but I can't make it work ;(

something's not right

It was painful but I think I made it work... I had to put logic to pick up specific js file in my index page (based on the build)

@pandeiro could it be that for some reason if I put :compiler-options to edn file they are ignored, but when they are passed to cljs task they are not? Or am I doing something wrong?

I have never put them in the edn file, not sure if it is supposed to work that way

okay

samples show that it supposed to, I guess I just do it in the task

Thanks!