This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-20
Channels
- # beginners (43)
- # boot (44)
- # chestnut (17)
- # cider (78)
- # cljs-dev (24)
- # cljsrn (16)
- # clojure (84)
- # clojure-dusseldorf (1)
- # clojure-italy (21)
- # clojure-losangeles (2)
- # clojure-russia (140)
- # clojure-sg (2)
- # clojure-spec (8)
- # clojure-uk (16)
- # clojurescript (23)
- # cursive (7)
- # datascript (1)
- # datomic (18)
- # docker (20)
- # ethereum (1)
- # fulcro (16)
- # garden (4)
- # graphql (27)
- # hoplon (9)
- # jobs (4)
- # luminus (34)
- # off-topic (6)
- # om (4)
- # onyx (35)
- # pedestal (3)
- # re-frame (24)
- # ring-swagger (15)
- # rum (6)
- # shadow-cljs (22)
- # spacemacs (8)
- # specter (22)
- # yada (7)
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.
@ag try sending them to target, then
Karma can pick them up
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?
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
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?
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
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 :-(
@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"