This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-21
Channels
- # adventofcode (82)
- # bangalore-clj (1)
- # beginners (44)
- # boot (7)
- # boot-dev (25)
- # cider (1)
- # cljs-dev (3)
- # cljsrn (14)
- # clojars (11)
- # clojure (210)
- # clojure-dusseldorf (4)
- # clojure-gamedev (2)
- # clojure-greece (11)
- # clojure-italy (6)
- # clojure-norway (6)
- # clojure-russia (6)
- # clojure-serbia (2)
- # clojure-spec (43)
- # clojure-sweden (1)
- # clojure-uk (77)
- # clojurescript (43)
- # cursive (1)
- # data-science (3)
- # datomic (32)
- # duct (3)
- # figwheel (2)
- # fulcro (71)
- # graphql (3)
- # hoplon (14)
- # jobs-discuss (3)
- # lambdaisland (1)
- # leiningen (2)
- # luminus (2)
- # lumo (14)
- # off-topic (16)
- # om-next (1)
- # perun (5)
- # random (1)
- # re-frame (19)
- # reagent (37)
- # ring-swagger (3)
- # shadow-cljs (157)
- # specter (6)
- # sql (29)
- # unrepl (14)
@bhagany just tried that but it still clashes with 0.4.2-SNAPSHOT and boot 2.6.0
@anantpaatra I hit the same problems and updated docs a bit, but didn’t deploy them cause I hit some deployment issue. But I’ll try to check out again. Try checking docs on github - https://github.com/hashobject/perun.io/blob/master/resources/guides/getting-started.md - I think that should work. I followed getting started guide 4 weeks ago
@podviaznikov Thanks! That indeed works, and now that I checked the only difference between it and the current website, the reason why became clearer. The website currently has the require instruction to be [perun "0.4.2-SNAPSHOT" :refer :all]
and the version on Github you just sent me has [perun "0.4.2-SNAPSHOT" :as perun]
so there is no conflict. Seems obvious now but I'm a noob so it took me this much to realize how to avoid that conflict. Thanks again 🙂
yeah, sorry about that. I can totally see how that was confusing. I went through tutorial myself and hit few issues
So the new boot introduced trace
which clashes with perun
, you need to avoid :refer
:all