This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-11
Channels
- # admin-announcements (1)
- # aws (2)
- # beginners (32)
- # boot (147)
- # capetown (1)
- # cider (11)
- # cljs-dev (45)
- # cljsrn (57)
- # clojure (187)
- # clojure-russia (5)
- # clojure-spec (97)
- # clojure-uk (33)
- # clojurescript (33)
- # cloverage (17)
- # clr (4)
- # conf-proposals (93)
- # core-async (6)
- # cursive (9)
- # data-science (1)
- # datomic (24)
- # defnpodcast (1)
- # devcards (3)
- # emacs (3)
- # hoplon (95)
- # jobs (1)
- # off-topic (7)
- # om (97)
- # onyx (32)
- # overtone (1)
- # parinfer (4)
- # pedestal (1)
- # proton (1)
- # protorepl (13)
- # re-frame (4)
- # reagent (10)
- # specter (14)
- # untangled (40)
Having problems updating dependencies for the contacts demo. I've got my own demos repository, so as to not destroy anything. Here's my updated copy of the contacts demo:: https://github.com/rolonicArk/demos/tree/master/contacts
Before the error, I get a warning: Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
@laforge49: could it be a clojure 1.9 issue?
I have run into issues before when using versions higher than the cljs version of boot-cljs
ie all my projects build against the 1.7.228
cljs version and 1.7
clj
not sure what changes are needed (if any) for proper support of higher versions since boot-cljs is only at 1.7.228-1
actually not even sure it matters, hmmm i would imagine that cljs should build against the same version as clj?
hahahaha
yeah should be 1.7.0
did that work tho? Is it building?
It would be nice knowing how these versions all play together
we need some table
@micha how does the boot clojure version work compared to project clojure version?
@flyboarder: boot clojure version is the version of clojure that will be loaded by boot, that's the one your build.boot runs in
if you have a clojure dependency in your project that's different it won't be loaded onto the classpath (because boot already loaded a different version of clojure)
so it shouldn’t affect things really except for running tasks
One thing I see a lot these days is exceptions because the mondue name is "undefined"
thats a new one for me
Thu Aug 11 12:14:03 EDT 2016 [worker-2] ERROR - handle websocket frame org.httpkit.server.Frame$TextFrame@427b93c6 java.lang.IllegalArgumentException: No method in multimethod 'handle-message' for dispatch value: null at clojure.lang.MultiFn.getFn(MultiFn.java:156) at clojure.lang.MultiFn.invoke(MultiFn.java:233) at adzerk.boot_reload.server$connect_BANG_$fn__261.invoke(server.clj:60) at org.httpkit.server.AsyncChannel.messageReceived(AsyncChannel.java:166) at org.httpkit.server.WSHandler.run(RingHandler.java:140) at org.httpkit.server.LinkingRunnable.run(RingHandler.java:120)
hoplon.firebase
now follows the 12-factor app config a bit, checks for existing env variables and auto init’s your firebase connection
it just chooses the transitive dependency that has the shortes path from the root of the graph
@micha @laforge49 depending on your version of windows, powershell has unicode support
PowershellV2 < HOST >Win7
I think my strategy is to revert to what works, upgrade the non-task dependencies and then show -p.
I just find it strange that all this is happening with something as simple as the contacts demo. 🙂
when apis are not stable there isn't much you can do other than deal with dependency hell
@micha: btw did you see? macro auto-infer is in cljs apparently
err, "implicit macro var"
http://blog.fikesfarm.com/posts/2016-07-03-clojurescript-clojure-namespace-aliasing.html
your boot task
although they also added many other unsavory things
> Now, there is a new simplification that will be coming to a ClojureScript compiler near you: You can use clojure as an alias for cljs in the first segment of namespaces in the case of nonexistent clojure. namespaces that can be mapped to cljs. namespaces.
ns macro language features and oddities continue to accumulate
maybe it's a good thing though
i think it's just hard to do with an embedded DSL like the ns macro, inside of which the semantics are not clojure's
easy to accidentally go crazy
like this works he says:
(ns foo.core-test
(:require [clojure.test :as test :refer [deftest is]]))
deftest is a macro there
clojure.test is rewritten as cljs.test
but yeah, doesn't have :refer :all still afaict
no clojure.test is rewritten to cljs.test by cljsc
you make a cljs namespace foo.bar
and in that namespace you do (:require-macros '[foo.bar])
it's not clojure's clojure.test lol
err i think i misunderstand
looking at http://dev.clojure.org/jira/browse/CLJS-1507 now, is that what you mean?
i see