This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-09
Channels
- # aleph (3)
- # beginners (327)
- # calva (3)
- # cider (20)
- # cljdoc (59)
- # cljs-dev (40)
- # clojure (104)
- # clojure-dev (30)
- # clojure-italy (8)
- # clojure-nl (36)
- # clojure-russia (3)
- # clojure-spec (3)
- # clojure-uk (79)
- # clojurescript (54)
- # community-development (5)
- # cursive (28)
- # data-science (21)
- # datomic (35)
- # emacs (14)
- # expound (1)
- # figwheel (2)
- # figwheel-main (82)
- # fulcro (18)
- # graphql (13)
- # jobs (12)
- # jobs-discuss (38)
- # kaocha (8)
- # lambdaisland (1)
- # lumo (12)
- # off-topic (20)
- # onyx (4)
- # re-frame (51)
- # reagent (12)
- # reitit (8)
- # ring-swagger (1)
- # shadow-cljs (22)
- # slack-help (2)
- # spacemacs (6)
- # specter (16)
- # testing (3)
An issue to be sorted: Quick Start page should be updated to 1.10.439, but we don’t have a standalone cljs.jar
for that release.
I think I found an analyzer regression in 1.10.439: https://gist.github.com/martinklepsch/9f885feb061ec3f03f365e22d0d9bf5b
I'll wait what ClojureScript maintainers say, usually turnaround on this kind of issue is pretty fast so maybe fine to wait.
And just using 339 could cause issues with users who use new stuff from 439 (assuming there is new stuff)
I'm somewhat surprised that this didn't come up before though. Not sure I understand but wouldn't this affect everyone using 1.10.439 and orchestra?
strange
Unfortunately it seems like *analyze-deps*
was rather important to be able to analyze namespaces that require react and similar
haha, no worries 😄
@martinklepsch this issue doesn't really make any sense to me
@dnolen the gist shows how ana/analyze-file
throws an exception in 439 that isn't thrown in 339
my description (macros, dynvars etc.) might be absolutely wrong, those are more guesswork
@martinklepsch yeah that won't work
duh, interesting I just copied that *analyze-deps*
thing mindlessly
Thanks, and sorry for the false alarm 😅
I changed *analyze-deps*
to true but now I'm having issues analyzing any namespace that transitively requires something like cljsjs.react
— is there something special that needs to be done for this to work?
No such namespace: cljsjs.react, could not locate cljsjs/react.cljs, cljsjs/react.cljc, or JavaScript source providing "cljsjs.react" in file file:/Users/martinklepsch/.m2/repository/reagent/reagent/0.7.0/reagent-0.7.0.jar!/reagent/impl/util.cljs {:tag :cljs/analysis-error}
@dnolen do build tools handle this by scanning the classpath for deps.cljs
? I guess I'll need to implement this in a generic way somehow (i.e. classpath->foreign-deps-entries
) — if you have any pointers around that I'd appreciate them 🙂