Clojurians Log v2

@bhauman Super excited about the work you're doing with the new clj tool. One thing I wanted to keep on your radar. For the purposes of working with web workers, I usually open up multiple figwheel repls by modifying the figwheel server port in the project.clj and then connecting back to each server from each worker. However, I have to set up different build IDs for each figwheel instance to prevent them from compiling over each other. Then I have each worker pull from the primary build ID root when they need to update.

dang how long has this channel been here

lol

What I'm hoping for is that with the new workflow, that an be a bit easier

@john the multiple build-ids problem woudl be solved by specifying different --output-dir's an the port is definitely going to be an option as well

@bhauman awesome! Thanks Bruce!

not sure if you saw this as well https://github.com/bhauman/lein-figwheel/issues/647

Awesome. For consistency purposes, I'd think that Figwheel's proxy relationship should be to CLJS just as ClJS is to CLJ. It would be neat if tools could consistently wrap one another like that. But that's just an initial impression. I'll take some time this weekend to investigate the different options your describing though.