This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-12
Channels
- # announcements (2)
- # aws (1)
- # beginners (63)
- # cider (2)
- # clj-kondo (1)
- # cljdoc (15)
- # clojure (114)
- # clojure-nl (1)
- # clojure-spec (15)
- # clojure-uk (10)
- # clojurescript (5)
- # clojutre (1)
- # community-development (6)
- # cursive (18)
- # data-science (1)
- # datascript (16)
- # datomic (2)
- # emacs (2)
- # events (3)
- # figwheel-main (2)
- # graphql (3)
- # jobs (2)
- # off-topic (23)
- # reitit (3)
- # shadow-cljs (27)
- # spacemacs (5)
- # sql (27)
- # unrepl (1)
I’m almost done getting all the basics in place for my new cljs / react native project. I got all the web audio / embedded webview stuff working, including injecting my clojurescript-compiled-javascript into the webview. (REPL inside that webview is working on iOS but not on Android; there it says “shadow-cljs - connection closed!“, but I didn’t yet look into that).
I’m currently trying to get binaryage/devtools
to work. According to the shadow-cljs user manual, if I understand correctly, all it should take is adding the dependency. It isn’t installed then though in my react-native target, and when I try to force it (`(devtools/install!)`) it says it is not installing under advanced builds. But I’m just running watch
, so that should not be an advanced build, right? Any ideas?
Oh wait that’s strange, after forcing recompile and having :autoload triggered, cljs-devtools is installed properly, but only because of the explicit devtools/install
that I have in there. :thinking_face:
@stefan.van.den.oord cljs-devtools is only installed automatically for the :browser
target. I'm not sure if react-native even supports it at all
btw you don't need to call install
or reference the devtools at all ... just add :devtools {:preloads [devtools.preload]}
https://github.com/binaryage/cljs-devtools/blob/master/docs/installation.md#install-it-via-preloads
And that preloads thing shouldn’t normally be necessary either with shadow (in browser) right?
Well you can still use “remote debugging” which works with chrome, so I’m actually hopeful that it may still work.
Not sure why initially it doesn’t want to install and mentions :advanced
, but I think I may have to look up in the cljs-devtools sources what kind of check they are doing for that.
you can disable the check via https://github.com/binaryage/cljs-devtools/blob/master/src/lib/devtools/util.cljs#L234
it looks like devtools.version
namespace is not present in your case, advanced build check assumes it gets munged