This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-22
Channels
- # beginners (17)
- # cider (3)
- # cljsrn (18)
- # clojure (76)
- # clojure-france (1)
- # clojure-italy (4)
- # clojure-nl (3)
- # clojure-poland (1)
- # clojure-uk (5)
- # clojurescript (33)
- # core-async (10)
- # datomic (31)
- # duct (5)
- # emacs (4)
- # fulcro (1)
- # graphql (5)
- # keechma (3)
- # off-topic (36)
- # onyx (1)
- # re-frame (4)
- # reagent (9)
- # reitit (9)
- # shadow-cljs (11)
- # vim (2)
my tests won't even compile with the latest clojurescript
"1.10.126" is fine though
@joelsanchez Even though 1.10.126 was also using AOT compiled ClojureScript compiler code by default, it might be worth checking if :classifier "slim"
addresses this issue (in other words, try the non-AOT)
thank you so much - it's working now
with your suggested change it works fine...but I don't know what was the problem
OK. If you end up tracking it down to anything minimal, a JIRA might be nice. (Perhaps we can get to the bottom of it.)
I'll try, it's weird because it only happens when running the tests with doo, normal compilation goes fine
I don't fully appreciate AOT failure modes—perhaps it takes something like Figwheel compiled against an older version or something like that in the stack to have AOT cause things to derail.
we are lucky, I have a minimal test for it
just trying to run doo fails with this error
well...doo is not needed, running tests is not needed either
just lein cljsbuild once "test"
fails!
I wonder if that could somehow be a combination of this https://github.com/emezeske/lein-cljsbuild/blob/7619af68f509eb74dd38de1968b33d0b940d1afb/support/project.clj#L15 and this https://github.com/clojure/clojurescript/commit/489dd729bb09c324e4028d4a73db5aa32b9483ab
will check it out. did a new repo for the repro (no pun intended) and updated the JIRA https://github.com/JoelSanchez/cljs-aot-cljsbuild-repro
(The hunch being that cljsbuild
involves AOT compilation against ClojureScript 0.0-3211.)
I tried that one but don't repro: https://gist.github.com/mfikes/4c7ed52e7ac9f4b5d092e0c315a4bee6
that's perplexing, I'll try to remove my local lein profile
tracked it down! 🙂 having {:user {:dependencies [[tubular "1.1.1"]]}}
was the issue
which turns out to be yours 😂
updated the repro @mfikes could you please try? it may be an issue with tubular?
Ahh, cool. I can repro it now @joelsanchez Let me take a look at what tubular
or its deps might be doing.
I'm going to try just copying the clj-sockets.core
namespace into tubular
and ripping out the clojure.core.typed
dep. Who knows what that might be doing
@joelsanchez Cool. ^ this works. I can cut a new release; just need to test that I didn't break tubular
by ripping clojure.core.typed
out of its clj-sockets
dep
👍 nice! glad to be of help will remove or close the jira after having dinner
Thanks @joelsanchez! [tubular "1.2.0"]
has been tested and published, sans clojure.core.typed
stuff (who knows what it was doing to things, but it was unnecessary for tubular
's core operation)
is using the name goog
as a local forbidden?
@gfredericks It doesn't appear to be verboten, but this kind of construct is not bueno
(let [goog 1] (goog/isArrayLike #js [1]))
Hello, I am trying to make infinite scroll with clojurescript and rum. I understand how to detect scroll bottom, but I don't know how to update rum component with new data and not rerender entire component. My component is simple (for [el (rum/react elements)]) and "on-bottom" I can do conj new data to elements list. So, how should I update component and not rerender all list?