It works reliably for me :) maybe I should do a screencast or something

Vim-figwheel helps

The frustrating thing is that it only works with the figwheel template... any other template/project and things seem to go south

vim-figwheel also seems to require that it is loaded after vim-fireplace... which pathogen does not accomplish:disappointed:

Yeah, it should probably move https://github.com/markwoodhall/vim-figwheel/blob/master/plugin/figwheel.vim#L6-L9

into autoload or something.

I appreciate your help here... I am trying to track down the root cause here so I can submit PRs to other templates like chestnut and luminus so I don't have to deal with this as much anymore

I've used it with chestnut. Let me grab chestnut and give it a spin 🙂

will log everything down

actually, good excuse to play with asciinema

Thanks @dominicm ... the JS-Workshop project I linked too is another puzzler -- especially since it is buy yogthos who is normally great at making stuff just work

oh jesus, when did chestnut change this 😧

https://github.com/bhauman/lein-figwheel/blob/250dcb6911d402609fe283afb3b98e081d068c3c/sidecar/src/figwheel_sidecar/repl_api.clj#L122 gotcha

@bfast Piggieback (figwheel-sidecar.system/repl-env (:figwheel-system reloaded.repl/system) nil)

Explanation: chestnut reached into the (internal?) api of figwheel, and moved the system. So the repl-env function no longer works. So this pulls it out of where they moved the figwheel system.

Lemme know if that fixes things for you

Gonna try load up the JS Workshop now

@bfast > lein new reagent-frontend reddit-viewer > cd reddit-viewer > lein figwheel This how I do the js workshop?

@dominicm I think you need to clone the whole project

then just attempt to run it in the cloned directory

okay, cool

I tried your piggieback command with chestnut... I got a NPE... When you launch "lein repl" in a chestnut project figwheel auto starts... so the timing may be off

I'll look into this later... have to go to work now 😞

@bfast Sorry, I should have been more precise.

lein repl

user=> (go)
user=> (cljs-repl) ; this may be optional

@bfast Regarding JS-Workshop: For whatever reason, figwheel doesn't write the .nrepl-port file, so fireplace can't auto-connect. So you have to do: :Connect manually, then scope the connection. From there, the normal figwheel piggieback works: :Piggieback (figwheel-sidecar.repl-api/repl-env)

Thanks dominicm- much appreciated , I will give this a shot

No problem. I've been through the pain of understanding all this crap 🙂. So I don't mind sharing

@dominicm what did you scope the connection to?

@bfast directory I had cloned project into

not sure what the scoping is for tbh, makes gf work maybe?

Ok -- I guess I am having problems once I connect to the figwheel repl... when I try cpp on an expression I get E605: Exception not caught: Fireplace: class java.lang.IllegalStateException... so I will keep investigating

@bfast On the JS workshop? In a .clj or .cljs file?

@dominicm yes JS workshop on core.cljs

one sec

Hmm, definitely working for me.

My lightweight test is :Eval (js/alert "hi") can you do that from core.cljs?

No I get java.lang.IllegalStateException

I am also not connected with Piggieback at this point

Piggieback from a .clj file before doing the :Eval

Recording my process now 🙂

https://asciinema.org/a/uajGXPnydtrsbaQieDbPPf9Za imperfect run-through

I think the problem is something with my environment... I don't need to do the .clj piggieback with the figwheel-template

That might just be because vim-fireplace is doing something with rhino on your behalf, but I'm not certain. You should always need to do the Piggieback

I need to do piggieback, but I can successfully do it in a cljs file in figwheel-template

oh interesting. Maybe Piggieback does work in a .cljs file, maybe it's something else... so now I am over-cautious and always do it in the .clj file 😛

Does my asciinema help at all?

I greatly appreciate your help... but i need to get back to work... I'll be online trying to debug this after work this week... this is driving me bonkers

I will check it out after work 😕

oh its not that long... ill take a look

nope, just trying to show order & stuff

Ok -- I don't have the ":Lein" command ... but I tried just running lein figwheel like you did and I was able to piggieback in and send an alert

my previous approach was to do "lein repl" and then start figwheel from the repl

for some reason that did not work...

sorry, my :Lein command just does lein figwheel in the background.

@dominicm Ok I think the root cause of this issue is that when invoking (start-figwheel!) from the repl you need to have ":repl-options {:nrepl-middleware [cemerick.piggieback/wrap-cljs-repl]}}" set in your dev profile

Adding that fixed this issue with my startup method

perhaps, yes. Makes sense. I suppose 🙂

I've found the boot method is far more sane, fwiw

boot instead of leiningen?

yeah. I know you're using pre-existing tooling.