Fork me on GitHub
#lein-figwheel
<
2017-02-01
>
zak11:02:42

I've got an issue in a cider cljs repl where figwheel tries to reload a changed file from the wrong path (omitting js/compiled/out)

zak11:02:47

Doesn't seem to be an issue running lein figwheel <build>, just from emacs M-x cider-jack-in-clojurescript

eoin17:02:15

Anyone else getting this In Chrome stable "Figwheel Client Version 0.5.8 is not equal to Figwheel Sidecar Version 0.5.9." Chrome Beta and Firefox are working well.

bhauman17:02:02

Make sure all your figwheel dependencies have the same version

bhauman17:02:29

And make sure you clean

bhauman17:02:46

And shift reload

bhauman18:02:10

@zak inside the figwheel repl print your config to see if it's different in cider

eoin18:02:31

@bhauman Sorry got it now. Shift reload. Thanks Bruce

devth20:02:46

when my figwheel reloads i get an error in chrome console:

Uncaught TypeError: Cannot read property '_reactInternalInstance' of null
    at figwheel_helpers$core$deep_force_update_BANG_
no luck debugging yet. om-next app. clues?

devth20:02:47

also noticed this (benign?) on reload:

Namespace figwheel.connect.public contains a reserved JavaScript keyword, the corresponding Google Closure namespace will be munged to figwheel.connect.public$

devth21:02:34

☝️ the issue was my build ID was "public" - renaming fixed

devth21:02:31

☝️ ☝️ previous issue Cannot read property '_reactInternalInstance' caused by not defonceing the om.next reconciler facepalm picard-facepalm facepalm picard-facepalm facepalm picard-facepalm facepalm picard-facepalm facepalm picard-facepalm facepalm picard-facepalm facepalm picard-facepalm facepalm picard-facepalm