for this I think you will need to open an issue on the project, probably a PR with some sort of "ignore this dir" option in boot-sass can solve it (few lines of code)...another workaround would be to position the task that adds node_modules after sass

right… trying that

but then… I can’t have @imports in my sass file that referes to anything in node_modules

uhm...right

gotttammit.... every time I think I’m out… they pull me back. I thought I’m done dealing with javascript-land mess. I guess I’m not

look, open an issue, the PR is simple stuff, I opened the code...it is better though to ask @juhoteperi what is the best course of action, maybe he has some other idea

also, you could use mathias/boot-sassc which has more control over what is compiled

thanks @richiardiandrea! I have created an issue and I’ll try mathias’s lib in the meantime. Although it’s deprecated

np 😉 hopefully this whole thing will help yourself and others (I'll follow the issue)

Is there anyone out there who could give me some help with my boot config?

@ag quite late to this party, but to give you some reasoning, the _ prefix is a standard in the sass community for indicating it's not an entrypoint.

Anyone know of a nice workflow for running tests via boot ? Maybe with a bit of spec magic show-cased ?

@pseud i’m a fan of running boot watch test (or boot watch speak test if you want pass/fail sounds)

the tests are re-run each time you save a file

i think the test task only does clojure.test tests though

but there are other boot tasks like boot-expectations, etc.

so far i’ve been satisfied with clojure.test, which is maybe not the most popular perspective 🙂

@grounded_sage sure what's up?

@pseud another testing option: https://github.com/metosin/boot-alt-test

Hmm, is it possible to wrap existing tasks in a pod (e.g. to add the dependencies that include the wrapped tasks)?

Is there any examples (that you know of) showcasing testing of a library that contains cljs, clj and cljc code ? I’m thinking I would want to exercise the cljc code (the api) in both cljs and clj mode to see if the platform-specific code holds up

@pseud: We're doing that here: https://github.com/workfloapp/macros

@jannis not possible. Somewhere there is a with-env option that sets the env before and after the task so that pods created by the task see a different env but thats more of a hack than a solution

@pseud: another example: https://github.com/daveyarwood/music-theory/blob/master/build.boot this library is cljc only, but the tests are run via boot-test and boot-cljs test to test both platforms

@martinklepsch Ok 🙂

err, it's a with-env macro ... 🙂

@jannis @dave - thanks a lot 🙂 I’ll get to analyzing those 🙂

https://github.com/boot-clj/boot/wiki/Snippets#task-environment-conflicts

hmm, I can’t find an example anywhere of passing command line args though a deftask

if I had (deftask foo [d debug bool “”] (comp (another-task debug)), how do I pass that debug into deftask another-task [d debug bool “”]?

I can just make another-task a regular defn, but that disallows me from calling it from the boot cli (without doing it through foo)

@lwhorton you can do like

(deftask foo
  [d debug bool ""]
  (comp
    (another-task :debug debug)
    ...

@micha a question, is there a way to add a directory to a fileset and then get it back so that I can write things in it? I know it would make it immutable, but I am trying to get around this while working on figwheel

the only super hack I found working is this horrible thing below:

user-resource-dirs (var-get (resolve 'boot.core/user-resource-dirs))
user-resource-dir (-> (user-resource-dirs) first)

aha, thanks @micha

@richiardiandrea not sure what you mean there?

basically I need to tell figwheel where to write, my first idea was to pass a tmp-dir to the fileset and pass tmp-dir

yeah that would be what i would do too

but the fileset will not include the tmp-dir, only a copy of it from what I see

(unless I am doing something stupid)

you can add the temp dir to the fileset

mmm I will try again, in theory that was my first idea, but it was not working as I expected

meaning (:directories (boot/get-env)) did not contain my temp dir

maybe you let figwheel go crazy in some directory

and you periodically poll that

by poll you mean use boot/sync-user-dirs! programmatically ?

hm i am probably not understanding the requirements

i guess it's all tightly coupled with figwheel

yes it is

so you can't really isolate it

exactly, I need basically to feed it a dir, then sync manually or use a dir already added to the fileset (this is why I was using boot.core/user-resource-dirs), moreover, figwheel only serves using resource-response

my workaround works but feels hackish...I wanted to understand if it is the only way out 😉

if something is writing to the fileset directories it could cause problems

those files are hard links to content-addressed blob files

so if you write to them the content is different

yeah that is what I was afraid of

but if I use a tmp-dir, then I need to find a way to say "hey, I changed the tmp-dir", please update my fileset

because from what I see the tmp-dir is not used directly but just "copied" in the fileset

(which makes sense given that the fileset is immutable)

hey guys… can someone guide me through writing my own custom task that uses dosh? For example I I want to run something like sassc src/sass/main.sass > target/css/main.css. I know there are community tasks that handle sass already. I just want to learn how to do this without. So as I understand I need to use with-pre-wrap fileset and then run dosh in there. But how do I grab result of dosh command and make commit!, not very clear

@ag you want to create a temp dir for your task to write files in

then you add that temp dir to the fileset

for example:

basically you have to have sassc or whatever write to a directory you make with tmp-dir!

then you can add that dir to the fileset

oh… ok… I’ll try to search for tmp-dir! in github. maybe find some sample snippets. thanks @micha

it's boot.core/tmp-dir!

snippet https://github.com/boot-clj/boot/wiki/Filesets#examples

ah yeah that's a good example

thank you guys!

👍 @ag !

hey guys.. dubbing into tmp-dir! why something like this would report that directory doesn’t exist:

(deftask sassc []
  (with-pre-wrap fileset
    (let [tmp (tmp-dir!)]
      (dosh (str "echo FOO! > " (.getPath tmp) "/foo.txt")))))

@ag that error is usually caused by subdirectories not existing when you try to create a new file

you will want to do something like (io/make-parents (io/file tmp "foo.txt"))

where io is

well in that case though i dunno

because the temp dir should exist

i don't think you're using dosh correctly there though

(dosh "bash" "-c" (str "echo FOO! > " (.getPath tmp) "/foo.txt"))

oh lemme try that!

bingo!

it worked!

thanks @micha

dosh doesn't pass the string to the shell

it does execv more or less

you want to call it with a program (`bash` in this case) and the arguments as separate strings

gotcha!

so… I have a dilemma to solve now… I have some sass files that @import stuff from npm packages . I need two tasks - one manages npm installs, second sass compilation. Independently is simple enough. But how do I make these tasks “talk” to each other? is there an example where fileset being “passed’ from one task to another?

@ag the preferred way is for the task to add a manifest/metadata file of some kind to the fileset, for subsequent tasks to find/consume

@ag I made a task for installing npm things degree9/boot-npm

@flyboarder yeah, as I said npm install by itself a trivial problem. but in my sass file let’s say I have something like @import “./node_modules/font-awesome/scss/font-awesome”. How do I make two independent tasks that deal with the same fileset?

how do I run npm task and then make node_modules available to be consumed in sass-task?

@alandipert where can I read/find samples about this?

so npm has its own sort of classpath, is that it?

how does @import know what to do?

well, let’s say I just do “npm install” and copy whole “node_modules” and commit that… something like:

(deftask add-node-modules []
  (with-pre-wrap fileset
    (let [nm ( "node_modules")]
      (when-not (and (.exists nm) (.isDirectory nm))
        (dosh "npm" "install"))
      (-> fileset
        (add-resource ( ".") :include #{#"^node_modules/"})
        commit!))))

this sorta “returns” a fileset innit?

so if I have that and this:

(deftask sassc []
  (with-pre-wrap fileset
    (let [tmp (.getPath (tmp-dir!))]
      (let [main-sass (->> fileset input-files (by-name ["main.sass"])
                        first tmp-file .getPath)
            out (str tmp "/css/main.css")]
        
        (.mkdir (java.io.File. (str tmp "/css")))
        (dosh "bash" "-c" (str "sassc " main-sass " > " out))

        (-> fileset
          (add-resource tmp)
          commit!)))))

because if main.sass contains a line that imports something ouf of node_modules - sassc task would fail with File to import not found or unreadable:

oh… I think I get it now… if I just (boot (comp (first-task) (second-task)) anything that first task commits into fileset would be available in second-task

❓ what’s idiomatic way of throwing a message that certain task should be always called in composition with another task?

you can use boot.util/warn for example

@ag the npm task i use copies the whole folder to the fileset so once everything is installed you can use sift task to filter out the things you don't want

@micha is there a way for tasks to receive metadata about the pipeline? Like to know if the reload task is being used?

❓ what’s the best way to find out if the fileset includes a certain directory?

boot.core/by-path?

@ag Probably. Also see other fileset filters: https://github.com/boot-clj/boot/blob/master/doc/boot.core.md#filter-sequences-of-tmpfiles

@ag the fileset is like git, it doesn't really care about directories

only files

so you can't have an empty directory in the fileset, for instance

@flyboarder usually you want to avoid directly coupling two tasks

ehmm.. guys… this is probably something totally unrelated to boot. but I haven’t seen this in lein-figwheel. I’m using pandeiro.boot-http and the initial load of first page is pretty slow. And it prints bunch of messages in nrepl-server buffer