Could you also run
lein deps :tree
and paste the output to the thread. It could be that one of your
dependencies is already depending on core.async transitively, and the
explicit inclusion of a different version of core.async causes that to
break. This is a long shot but it could help.
On 20
Daniel, is the UI constructed based on receiving something from a
channel? which is incorrectly setup and so the UI is 'blocked' pulling
from that channel.
Timothy Baldridge writes:
core.async has nothing to do with the DOM, so I don't know how this could
happen.
On Wed, Aug 19, 2015 at 3:00
I've found that using core.async in one of my projects results in the
entire DOM getting replaced with an empty iframe when I view the site in
Firefox. I'm using
[org.clojure/clojure 1.7.0]
[org.clojure/clojurescript 1.7.48]
[org.clojure/core.async0.1.346.0-17112a-alpha]
I've tried
Would you mind pasting the rest of your dependencies? This is the most
curious of puzzles and I'd love to know the answer - but I'm really stumped
so please provide the next clue!
On Wednesday, 19 August 2015 19:32:22 UTC+1, Daniel Higginbotham wrote:
I've found that using core.async in one
core.async has nothing to do with the DOM, so I don't know how this could
happen.
On Wed, Aug 19, 2015 at 3:00 PM, Malcolm Sparks malc...@juxt.pro wrote:
Would you mind pasting the rest of your dependencies? This is the most
curious of puzzles and I'd love to know the answer - but I'm really
Here you go!
[[org.clojure/clojure 1.7.0]
[org.clojure/clojurescript 1.7.48]
[org.clojure/core.async0.1.346.0-17112a-alpha]
[adzerk/bootlaces 0.1.11 :scope test]
[adzerk/boot-reload0.3.1 :scope test]
[pandeiro/boot-http0.6.3
