Hello! I would like to use Figwheel Main, but can't find any docs, how to connect to REPL started by Figwheel Main from Emacs/Cursive? Is there any guides how to open nREPL port from REPL started by Figwheel Main?

I’m a bit confused about configuration, and specifically what should be in the map and what should be in the metadata of the map

is the map the config that’s passed to clojurescript?

is that documented somewhere?

@mike1452 How are you setting up your project? Lein? or clj? or boot?

for clj I followed the tutorial in figwheel-main and just used Cider-jack-in-cljs and it worked.

@jduhamel Hi! I'm using Clj CLI + Spacemacs. Where did you find such tutorial? Here? https://cider.readthedocs.io/en/latest/clojurescript/

@stathissideris https://figwheel.org/docs/create_a_build.html

but yes only ClojureScript options are in the body of the map

and figwheel options are in the metadata

https://figwheel.org/config-options

but perhaps I could make that more explicit

@bhauman thanks, but I’m mainly wondering about where I can find information about the options that go into the map

I did find the documentation on the figwheel options (very complete documentation btw, I’m impressed!)

but what are “ClojureScript options” 🙂

I suppose that would be on the clojurescript website somewhere

@stathissideris its linked to on the create a build page

but I’m sure if you search for Clojurescript compiler options it will come right up

https://clojurescript.org/reference/compiler-options

@bhauman Hello, Bruce! Is there any tutorial, how to connect to REPL from Cursive, which run by Figwheel Main?

@mike1452

not yet but its pretty straight forward

start a repl of some kind in cursive

I use Clojure CLI

https://figwheel.org/docs/scripting_api.html

so you will want to start a REPL in cursive

you will then use the scripting api to start figwheel

@bhauman Thanks. Now a bit more clearer. But, when I run (figwheel.main.api/cljs-repl "dev") it hangs my REPL in Cursive and Chrome console tells me "WebSocket connection to '<ws://localhost:3449/figwheel-ws/dev>' failed:"

@mike1452 that error is wrong

that error is for figwheel-sidecar

so something is wrong

@bhauman I always used lein-figwheel and it works very straightforward. Now, I'm trying to migrate my configs for Figwheel Main and I think I mixed some configuration for both (lein-figwheel and Figwheel Main). I'm trying to achieve next workflow: 1. Run REPL using clojure CLI from terminal with Rebel support 2. Run Figwheel Main and switch REPL from CLJ to CLJS mode 3. Connect to REPL from Cursive or Spacemacs using remote connection 4. have fun with coding CLJS and FigWheel and eval sexp from IDE, not terminal It would be nice to have such guide

@bhauman thanks, and sorry, I hadn’t seen the link! I think I was just missing the name for it (“compiler options”)

@zane this is kindof a bug in figwheel right now

I think this happens because when figwheel is loading it takes over the loading of dependencies at that point

and dependency loading becomes async and not sync as usual

I’m planning on fixing this

but its only a problem in when figwheel is included

hmmm I could probably fix this with a setTimeout 0 since everything is synchronous

@bhauman i've made a little progress in debugging my lein fig;test issue: By using -pc and looking at the source I found the reason my :output-dir changed in my client's code, but not in the template code: It's because in the template code example the :dev profile has :resource-paths ["target"] which causes should-add-temp-dir? to be false in https://github.com/bhauman/figwheel-main/blob/master/src/figwheel/main.cljc#L559 By adding (in my client project.clj) :resource-paths ["target"] now :output-dir/:output-to are the expected [Figwheel] Compiling build test to "target/public/cljs-out/test-main.js"

The next problem is that while I mimic what the template does by creating a test HTML file in resources/public/test.html when running the test (using the example in test.cljs.edn of :open-url "http://[[server-hostname]]:[[server-port]]/test.html") the actual URL is not found?

The symptom is that the test hangs at:

Launching Javascript environment with script:  ["/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" "--headless" "--disable-gpu" "--repl" :open-url]
Environment output being logged to: target/public/cljs-out/test/js-environment.log

tmarble@tmarble 43 :) ps -ef | grep headless | grep -v -E '(Helper|grep)'
  502 97428 97424   0  2:23PM ttys002    0:00.98 /Applications/Google Chrome.app/Contents/MacOS/Google Chrome --headless --disable-gpu --repl 
tmarble@tmarble 44 :) 

And trying to load in a normal browser tab shows: Figwheel Server: Resource not found Keep on figwheelin' yep

OMG I fixed the this last problem by completely commenting out... (from the client project.clj)

;; Avoid contamination of AOT artifacts (e.g. during uberjar) vs dev artifacst
  :target-path "target/%s/"

I can't tell you how SWEET it is to see this!

Ran 7 tests containing 15 assertions.
0 failures, 0 errors.
:figwheel.main.testing/success

getting coworker up connecting to clj -A:fig:build and he's not sure which port to direct cursive at. does anyone know?