Clojurians Log v2

Anyone had sucess enabling jetty's :async true in figwheel handler config (`:figwheel-options`)

@isak your websocket url is blank??

@bhauman : yea :thinking_face:

@isak what does your config look like?

@samueldev: i have a figwheel.edn that looks like this:

:http-server-root "public"
 :server-port 3449
 :builds-to-start ["dev"]
 :builds [
          {:id "dev"
           :source-paths ["src" "dev-src" "test-src"]
           :figwheel { :on-jsload "front.tests.runner/run" }
...

running it via sidecar. it is strange, because it was working before, and I don't think i've changed anything or even upgraded dependencies

@isak is this a node env or worker env or html env?

@samueldev : html

what browser?

chrome

also windows

hey @bhauman I'm trying to get set up to do some work on figwheel (and to further look into what @isak is describing) - simply running ./scripts/install doesn't seem to be making my cljs projects use my locally installed figwheel, any idea why? is there a dev guide anywhere? (didn't see anything in the readme)

your dev project needs to point to the installed SNAPSHOT version?

yeah it is, but I forgot to lein clean 😛 sorry to bug

no worries, this is all part of it