Hi all, I’m sure this is something easy, but can’t seem to find it - how can I tell boot to create actual files? For example, if I do (cljs :optimizations :advanced), it compiles successfully and makes the js files available to other tasks like serve, but I don’t see the js file anywhere on disk? How can I tell boot to write the actual compiled js file to disk?

maybe the sift task is the way to go? maybe sift it into a resources/public directory or something like that?

@upgradingdave use the target task

e.g.: (boot (cljs :optimizations :advanced) (target))

ah, sweet, perfect, thanks!

@upgradingdave you can also customize the directory where the files will end up with (target :dir “foo")

the default being “target"

can I call e.g. sift inside with-pre-wrap?

if not, how do I remove a file from the fileset?

@anmonteiro you cannot use sift

@anmonteiro the fileset is a map/record with a :tree key. Keys are paths and values are describing files at that path. Dissoc a key to remove a file

(make sure you also commit! the changed fileset value)

@martinklepsch awesome

seems simple enough

yep 🙂

@martinklepsch hrm, would this be possible?

(deftask foo []
  (comp (with-pre-wrap fileset ….)
    (sift ...)))

@anmonteiro yes

with-pre-wrap generates a function AFAIK

ok, cool

also a viable option then, thanks

you're welcome 🙂

hrm

shouldn’t find a file in the classpath for me?

boot.core/by-re should be able to do what I want

io/resource will find a file on the classpath

the by-re function filters a collection of TmpFile objects though, not classpath

it's for filtering the fileset