dammit, why everything is so complicated? every time I need to cross the bridge to awful hell of javascript nightmare I have to deal with so much nonsense and pain. and Boot's filesets not helping at all, FWIW - the tangle things even more. I feel so stupid.

is there really nobody here who ever used boot-cljs-test with Karma to run tests in Chrome? I basically want to re-run tests with watch.

but I can't make it run them even once

stupid piece of horse manure can't locate compiled js files

@ag try sending them to target, then

Karma can pick them up

well, test-cljs seems to be doing something with the fileset

This:

(boot
  (comp
    (test-cljs)
    (target)))

there's nothing

I tried setting tasks :update-fs? to false and true - and still nothing

I can't figure out what exactly to put into karma.conf.js

Nope, forget all about testing for now

To a first approximation, boot-cljs-test runs doo https://github.com/bensu/doo/

If you want to run Karma tests directly then you need to write your own karma.conf.js

and call Karma directly

Doo can run Karma, but it's not very flexible, and doesn't let you provide plugins

Take a look at https://github.com/Day8/re-frame/blob/master/karma.conf.js for an example in lein

It should be almost exactly the same for boot, apart from the output file locations maybe

Created an issue for large number of directories erroring out on OSX: https://github.com/boot-clj/boot/issues/641 Anyone seeing similar in other environments?

hi, i think boot-cljs-repl should support node.js

i traced the reasoning back to the original issue: https://github.com/adzerk-oss/boot-reload/issues/12

the :ids solution is more than enough to solve this problem, and there's no reason people can't target nodejs and still want reload and repl functionality, especially with electron

@cjhowe as a workaround, boot-figreload might work for your use-case.

looks like it's not filtering :target :nodejs, so i'll give it a try

oh, it still uses cljs-repl which has the same issue

here are the PR's that changed this: https://github.com/adzerk-oss/boot-cljs-repl/pull/11 and https://github.com/adzerk-oss/boot-reload/pull/11

i'm surprised no one has had an issue with this for over 2 years! i guess no one is using boot with node.js?

That's it pretty much. Not that many people are targetting node.js at all

what are the largest single person clj projects ?

@qqq wrong channel? 😛

sorry, I thought I was in #off-topic

Hello, I have a task which have a watch in it. Can I defer it or run in background so I can go back to my repl?

@vinnyataide typically what i do is start a repl with :server true :port 12345 and connect to it from another terminal with boot repl -c -p 12345

what i mean is:

(deftask the-task-with-the-watch
  []
  (comp
    (watch)
    (do-stuff-when-files-change)
    (repl :server true :port 12345)
    ...))

so your task with the watch is primarily for doing stuff when the files change, and then in another terminal you can connect to the repl with the -c (client) option and have a dedicated repl process

all right, thank you, that's what I thought, though I use the internal boot repl which opens by default and set with task options to a known port

Are there any known Windows-specific issues with Boot 2.7.2?

pandeiro i remember reading something about a regression in uber, but i might be misremembering

of course i don't think i made an issue either :-(

No worries, it seems like it may have been a phantom report on my side, too :)

#fixed

@pandeiro I haven't digged into this, as I don't windows, but I have a suspicion that virus scanners might confuse boot due to the creation of temp files + them not being usable until virus scanner says "clear"

Wow @dominicm, thanks for that theory. I will in fact pass that on as "maybe a thing". 👍

(I saw this a few times on training courses, with errors that were "file not found")