Fork me on GitHub
#re-frame
<
2021-11-02
>
Arun16:11:15

Hey guys, i’m having an issue with re-frame-10x where it pops up for just a second and then it errors out. I’m currently using shadow-cljs:

p-himik16:11:33

There should be more context above.

Arun17:11:33

what context do you mean?

Arun17:11:33

that’s all the relevant info that’s above the screenshot

p-himik17:11:50

An error occurred when loading re_highlight.core.js - there should be some context to what error happens exactly. Maybe it's above, maybe it's within, maybe it's within something that's below.

Arun17:11:33

does that help?

thheller18:11:14

maybe try upgrading shadow-cljs. at the very least the error should be slightly clearer.

Arun18:11:04

my shadow-cljs is currently 2.15.12

thheller18:11:34

that error you get is not from 2.15.12

thheller18:11:18

do you use project.clj or deps.edn to manage your dependencies? if so you maybe only upgraded the shadow-cljs npm package but not the dependency there?

Arun21:11:37

i use deps.edn

Arun14:11:58

@U05224H0W here is my deps.edn:

{:paths
 ["src/dev"
  "src/main"
  "src/test"]

 :aliases
 {:cljs
  {:extra-deps
   {thheller/shadow-cljs        {:mvn/version "2.15.12"}
    re-frame/re-frame           {:mvn/version "1.2.0"}
    kee-frame/kee-frame         {:mvn/version "1.3.1"}
    akiroz.re-frame/storage     {:mvn/version "0.1.4"}
    applied-science/js-interop  {:mvn/version "0.3.0"}
    com.fulcrologic/guardrails  {:mvn/version "1.1.5"}
    day8.re-frame/tracing       {:mvn/version "0.6.2"}
    day8.re-frame/re-frame-10x  {:mvn/version "1.1.13"}
    day8.re-frame/async-flow-fx {:mvn/version "0.3.0"}
    metosin/malli               {:mvn/version "0.6.0"}
    fork/fork                   {:mvn/version "2.4.1"}
    meander/epsilon             {:mvn/version "0.0.602"}
    expound/expound             {:mvn/version "0.8.9"}
    reagent/reagent             {:mvn/version "1.1.0"}}}}}

thheller19:11:21

thaty is very odd since the screenshot you posted is definitely not from 2.15.12. I changed the way that specific error message looks to make it clearer in 2.15.11

thheller19:11:50

did you maybe not restart shadow-cljs after adjusting the version?

Arun20:11:14

which screenshot are you referring to? the first or second? either way it’s giving me the same error after restarting

Arun20:11:58

there’s also this error:

thheller20:11:03

the screenshot with "An error occured when loading ..."

thheller20:11:13

that error message is different now

thheller20:11:22

that other error is just a symptom of the first

Arun20:11:04

That loading error didn’t change at all for me

thheller20:11:21

you do have :deps in your shadow-cljs.edn right?

thheller20:11:13

that error message changed so I don't understand how you are getting that message still

Arun20:11:25

this is at the top of my shadow.cljs

:deps {:aliases [:cljs]}

thheller20:11:16

and when you start shadow-cljs it actually prints the 2.15.12 version?

Arun20:11:45

[shadow:watch ] shadow-cljs - HTTP server available at 
[shadow:watch ] shadow-cljs - server version: 2.15.12 running at 
[shadow:watch ] shadow-cljs - nREPL server started on port 51321
[shadow:watch ] shadow-cljs - watching build :app
[shadow:watch ] [:app] Configuring build.

thheller20:11:23

and you are loading the output of that build? not some old lingering js file?

Arun20:11:05

i believe so, how do i clear the old lingering js file to make sure?

thheller20:11:15

(eg. maybe you changed :modules or :output-dir?)

Arun20:11:47

Yep that was it

Arun20:11:58

i changed :modules

Arun20:11:04

thanks for the help