This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-31
Channels
- # adventofcode (15)
- # announcements (3)
- # babashka (38)
- # beginners (121)
- # calva (29)
- # cider (21)
- # circleci (1)
- # clojure (177)
- # clojure-europe (7)
- # clojure-france (2)
- # clojure-nl (7)
- # clojure-spec (3)
- # clojure-switzerland (5)
- # clojure-uk (4)
- # clojurescript (10)
- # code-reviews (1)
- # conjure (19)
- # deps-new (2)
- # emacs (5)
- # fulcro (52)
- # graalvm (13)
- # kaocha (1)
- # malli (1)
- # off-topic (6)
- # pathom (5)
- # re-frame (17)
- # reagent (14)
- # remote-jobs (1)
- # rewrite-clj (5)
- # robots (1)
- # shadow-cljs (13)
- # sql (38)
- # tools-deps (16)
- # xtdb (99)
Hi there! I’ve picked up a side project and started using awesome ShadowCLJS again. I’m trying to figure out something but I’m having a hard time. I’m hoping someone here can give some advice. I’m building a :browser
target for use in an iOS / Android web view. On iOS I have it working. On Android there’s the issue however that Android has 10.0.2.2
as IP address of the host running the development environment, not localhost
. So what I’m observing is that the initial load of my compiles JS bundle is working (because I load it from 10.0.2.2
, but then ShadowCLJS tries to connect to localhost
. I’ve tried setting :devtools-url
` to
, but then the websockets upgrade doesn’t work (“error during websocket handshake: unexpected response code: 200”). I have the feeling that it should be possible somehow, but how…? Thanks for any help / pointers!
While ruminating this over breakfast, I realized that I already knew the solution, just didn’t think of it at the right time. Like the manual says, :devtools-url
should point to the primary server. So it should have been
. After changing that it worked. 🎉
@thheller Thanks, useful to see. I’ll play around with :esm and see what I can get going.
What is supported by :browser
but not by :esm
?
What are the 2 PR’s going to allow for? Will they enable mograting away from goog.provide
?
the output will look like :esm
currently but a little cleaner I guess. goog.provide
is never part of an optimized build so I'm not sure what you mean. CLJS will continue to use that for a while.
@thheller is there a way to access the lein project name/version programmatically from within the app?
for instance, in jvm clojure, I can do (System/getProperty "attribute-service.version")`
Is there any reason I should use browser over esm for browser target?