Nope not yet. :)

Let me get some more details...

I'm behind a corporate HTTP proxy currently, if I specify proxy details as follows in my projects local shadow-cljs.edn it works fine:

I assume by proxy you meant the :proxy in shadow-cljs.edn for dependency resoltiuon?

{:source-paths
 ["src"]

 :proxy {:host "127.0.0.1" :port 3128}
 :nrepl {:port 9000}

 :dependencies
 [[cider/cider-nrepl "0.25.8"]
  [reagent "1.0.0"]
  [re-frame "1.1.2"]]

 :builds {:app {:target     :browser
                :output-dir "public/js"
                :modules    {:main {:entries []}}
                :devtools   {:http-root "public"
                             :http-port 3000}}

          :prod {:target     :browser
                 :output-dir "public/js"
                 :modules    {:main {:entries []}}
                 :release    {:compiler-options {:optimizations :simple}}}}}

yeah that should be :maven {:proxy ...}

Correct.

ah!

cool!

that'll then work in the other config too

nice! 🙂

Thanks for the help!

btw the :prod build is an anti-pattern in shadow-cljs

just put the :release bit into the :app config

optimizations are only applied to release builds so it does not affect the watch or compile builds

Ah got you! Thanks for the spot.

Learnt something new 🙂

yeah common mistake people make that have used other tools before (or read other docs) 🙂

Would you then just do shadow-cljs release app ?

yes

Cool

The proxy still doesn't seem to work globally set.

This is what I have set:

{:mvn {:proxy {:host "127.0.0.1" :port 3128}}}

file-path is: /home/rameezk/.shadow-cljs/config.edn

:maven not :mvn

That look right?

ah cool

Apologies, that works 🙂

I’m adding `{:closure-defines {"shadow.cljs.devtools.client.env.server_host" "%IP-ADDRESS%"}}` to `(shadow/watch options)` to set correct IP address

what the heck does this do? is this some kind of trick I don't know about? what is %IP-ADDRESS%? or do you just set the actual IP there?

Hi @U051091NM, how can I get the IP address? Is it the IP of the emulator? I don't know how to get the IP

%IP-ADDRESS% is a placeholder for your machine real ip

{:closure-defines {"shadow.cljs.devtools.client.env.server_host" "192.168.1.111"} for instance

@thheller server_host is used here https://github.com/thheller/shadow-cljs/blob/3e559b8f9ea80cc1ad1c51772fe4aa8c099a1159/src/main/shadow/cljs/devtools/client/env.cljs#L84 if not set, it uses “localhost” which doesn’t work in iOS simulator (it needs ip address to connect)

@UNL0HK5ME It needs to be IP address of your host machine (where shadow-cljs is running), on mac you can get it with ipconfig getifaddr en0 where en0 is your network interface

@U051091NM well for react-native there is :local-ip "1.2.3.4" in your build config or via config merge. going through closure-defines is kinda backwards. just thought there was some magic %IP-ADDRESS% placeholder or something that metro will replace but I guess not.

Thanks @thheller Nice to know there is local-ip option. At the time i was adding hack with server-port override, it wasn’t there i think.

that has always been there, just not documented. I don't do react-native myself so the entire section of the code and docs is lacking a lot of clarity 😞

@U051091NM thanks! I will try that one. The whole time I'm thinking shadow and emulator are running in localhost. I want to dig more into the architecture, do you have recommended resources that I can read?

Thanks! it works now by specifying the LAN IP. If I understand correctly now, my laptop running the shadow-cljs and emulator will be two device connected to the LAN. When shadow-cljs runs in localhost, the websocket client running in the emulator tries to connect to localhost which is then the emulator not my laptop? Where the solution to put the specific IP will make the websocket client point to my laptop LAN IP which is where the websocket server is running right?

Yes, client running in the emulator needs IP to connect to server which is running on your laptop

technically it doesn't use localhost by default for react-native. it uses the IP it gets from your system. specifically this part of the code

https://github.com/thheller/shadow-cljs/blob/23dcd7724681f9ba7c64530735385b06549266f6/src/main/shadow/cljs/devtools/api.clj#L588-L623

but if your machine has multiple IPs it sometimes picks the incorrect one. still need to tune that mechanism a little I guess.

but yes, your emulator has a different IP and connects over the "network" not localhost

Thanks @thheller @U051091NM for these pointers. I learned something new again