This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aleph (3)
- # beginners (37)
- # boot (45)
- # carry (1)
- # cljsrn (15)
- # clojure (78)
- # clojure-austin (2)
- # clojure-brasil (10)
- # clojure-czech (3)
- # clojure-dev (12)
- # clojure-dusseldorf (31)
- # clojure-hamburg (2)
- # clojure-italy (4)
- # clojure-poland (2)
- # clojure-russia (37)
- # clojure-spec (25)
- # clojure-uk (30)
- # clojurescript (160)
- # cursive (40)
- # data-science (1)
- # datomic (31)
- # emacs (7)
- # figwheel (4)
- # hoplon (73)
- # leiningen (1)
- # liberator (5)
- # luminus (7)
- # numerical-computing (1)
- # off-topic (31)
- # om (89)
- # onyx (66)
- # proton (5)
- # protorepl (1)
- # re-frame (18)
- # reagent (2)
- # ring (2)
- # spacemacs (1)
- # untangled (93)
- # vim (19)
- # yada (67)
is there a reason the default global BOOT_CLOJURE_VERSION is 1.7.0 instead of 1.8.0? am I going to shoot myself if I set it to 1.8.0 permenantly in my environment?
odd that it didn’t update it. i went through homebrew. wonder if I need to uninstall and reinstall it.
i’m finally giving comparing lein and boot a shot, I don’t know a huge amount about either.
Sometimes when starting up my project (`boot dev`) I see random errors like this one:
java.lang.RuntimeException: No such var: async/remove<, compiling: (my.code) But obviously that var exists. Usually if I restart the process, it works again.
I think it's a kind of timing problem or race condition as it happens more often when the system is doing something in the background at the same time (e.g. starting up datomic)
I"m not sure if it's about clojurescript compilation or the clojure part of the system.
there any downsides/caveats on having a project.clj for figwheel/frontend only to mix with a boot project?
@naomarik > for figwheel/frontend only I don't understand why you wouldn't just do it in boot (boot can do a figwheel setup too!) --- You will need to make sure that target is different for leiningen and boot if they're running as siblings.
https://github.com/adzerk-oss/boot-cljs-example gives a setup which works the same though. HUD and everything 🙂
Apparently it's not quite as good at reporting error messages in a pretty way, but otherwise it's the same.
yeah using boot cljs but i recently saw figwheel's errors and looked immensely easier
@naomarik I've never been able to figure out the significance of difference in reporting. Could you describe the big improvement to me?
@dominicm I've not really used figwheel much, been using boot-cljs ever since I started because at that time I couldn't for the life of me get my repl connected to figwheel. I just recently ran a new figwheel project to see what it has and it shows your source code in the browser with a helpful message, so it looks a lot easier to pinpoint silly mistakes
the screenshot the figwheel has on the project is out of date to what it actually looks like now
@naomarik I've never really seen that as much more useful. I look at the line number of the error, and go to it in my editor, and look there.
Yeah, I know the screenshot is outdated. I was hacking on Figwheel recently, so I have used it.
https://github.com/adzerk-oss/boot-cljs/blob/master/src/adzerk/boot_cljs.clj#L160-L163 looks like these lines add metadata to the fileset when there's a warning in compilation. You could look at how figwheel finds the source and open a PR to attach this in the metadata.
Is there anyway I could fake something like
(ns ^:figwheel-always ) with boot-reload / boot-cljs?
I'm experimenting with
:recompile-dependents false on our cljs compilation step which has significantly improved reload times, but our test-runner needs to always act like it's reloading.