I don't understand the https://figwheel.org/config-options#connect-url option. I have put :connect-url "" in my figwheel-main.edn but it keeps connecting to localhost:9500 which is not where the figwheel server is running

hah, now it started working all of a sudden.. after upgrading to 0.2.11, weird

so now I kinda wish I could set that IP using some environment variable because this IP will be different for every of my colleagues

where can I configure the JS/CLJS function that should be called after reloading sources?

Found it here: https://figwheel.org/docs/hot_reloading.html I expected this to be part of the figwheel-main.edn file without having to change my source code.

I guess figwheel doesn't come with any CSS/less magic other than reloading the CSS right?

@borkdude yes that’s right

ok, that's fine. I solved that problem. My only remaining thing is be able to set :connect-url dynamically, based on some env variable for example

for anyone curious, I'm using this for less:

:less/dev {:extra-deps
                      {deraen/less4clj {:mvn/version "0.7.4"}}
                      :main-opts ["-m" "less4clj.main"
                                  "--auto"
                                  "--source-map"
                                  "--inline-javascript"
                                  "--source-paths" "resources/public/css" "--target-path" "target/public/css"]}

The docs for :connect-url aren't entirely clear to me. It speaks about "server side" and "client side". but :connect-url is only used from the browser to connect to the websocket server, right? so why all these options for "server side"?

I think I just need :connect-url "ws://[[client-hostname]]:9500/figwheel-connect" - seems to work for me

@borkdude cool I’m glad you found something that worked

@borkdude the server-hostname stuff is helpful if you are listening on a certain eth address and that happens to be address that your client is using

really glad you are taking the new stuff for a spin

is this new? I haven't been following for a while 🙂 I'm porting the CLJS and less build from boot to deps.edn

oh this isn’t new

I thought you might be trying out the new :target :bundle support for npm deps

there is also HTTPS support

I might, but probably not for this project because my team lead is not fond of npm...

just good old foreign-libs and cljsjs

it's good to have support for it though. I'm glad all is working now together with our old boot stuff, hybrid

well that stuff works and works well enough for sure!