@augustl so you are running figwheel with 1.11.51 without a problem?
It seems that figwheel-main is having a problem with 1.11.51. Is anyone else seeing this?
Yes. Haven't had time to isolate what it is.
@bhauman I actually only tested minified compiling, I didn't run it in dev mode yet
if you do I think you will notice a missing clojure.data.json dep. which you can simply add to your deps. Then you might see a problem where cljs is missing a vendor/bridge file.
I just need to confirm that others are experiencing this.
yeah, I got that error, and in complete braindead mode without any research or thinking I just added [org.clojure/data.json "2.4.0"] as a dependency. Everything seems to work fine, just started it up in "dev mode" as well 🙂
@augustl are you starting a repl in dev mode? because that’s when the error occurs.
yeah, it's in dev mode
vendor/bridge is in the stacktrace, and my initial (few minute) investigation had it happening in piggyback.
Thanks for looking. Yeah its not in piggieback. It’s in Clojurescript when it starts a repl. It’s trying to dynamically load a file vendor/bridge.clj from the classpath and can’t find it.
@bhauman is this specific to Piggieback though (since I didn't see this w/ plain usage), I see that Piggieback uses nREPL interruptible eval and there might be classloader tricks interfering? maybe way off base, but hard to think of how this could fail otherwise
@dnolen Nope unfortunately not piggieback because I’m not using it
I’m using plain jain clj with figwheel in a minimal project
I also dissabled all classpath munging
@bhauman you could try changing to (require 'cljs.vendor.bridge) in ClojureScript
then ./script/build from ClojureScript repo
and then note the artifact name
if that works then can switch to that
I changed it but the change isn’t taking with script build?
@dnolen ^
what does that mean? you just end up seeing the same problem?
No I mean I’m using the Clojurescript build process and its not picking pu my changes in repl.cljc
do I need to make a commit?
like you look inside the JAR and it's not there?
It’s inside the jar.
make sure you blow away target, you should not have to do that but just in case
OK
and try again
I added some stuff to print the classpath and see what the classloader is
@dnolen as suspected the (require 'cljs.vendor.build) fixes it, I double and triple checked it.
@bhauman k, fixing and releasing now
Thank you!
https://github.com/clojure/clojurescript/pull/179, waiting for tests to pass
Thanks man
I still do and have always loved the the ’wheel
building / releasing 1.11.54
just released figwheel-main ‘0.2.18’ that includes the clojure.data.json dep