Fork me on GitHub
#shadow-cljs
<
2023-04-23
>
Sam Ritchie16:04:38

does anyone know how to silence these closure warnings?

--------------------------------------------------------------------------------
------ WARNING #38 -  ----------------------------------------------------------
 Resource: node_modules/shadergraph/src/visualize/markup.js:143:56
 String continuations are not recommended. See 
--------------------------------------------------------------------------------
I couldn’t find this one in the clojurescript docs

thheller16:04:09

there is no setting for that

Sam Ritchie17:04:27

I found these ones, just not this particular warning. interesting

scaturr17:04:32

Is there some documentation on known gotchas around the repl? shadow-cljs is incredible, but every now and then I’ll run into a hiccup that causes the repl to break. This also happens often when I refresh the page. If I run into a “Timeout while waiting for result” message, is there a way to recover from this that doesn’t involve restarting the repl?

thheller06:04:45

timeouts you get when the evaluation runs for too long. it defaults to 30sec, but can be increased via :devtools {:repl-timeout 60000} in the build config. timeout value is msec.

thheller06:04:09

if you provide more specifics about the other stuff I can maybe make suggestions?

thheller06:04:25

refreshing the page will lose all evaluation context, so that is expected

thheller06:04:43

don't know what you mean by REPL breaking, you sure its the REPL and not your editor?

scaturr12:04:43

Perhaps I meant “lose all evaluation context” when I said breaking. I primarily use Calva, and I have had times where after refresh I can re-evaluate a namespace without issue. Yes the previous state is gone, but I can continue using the REPL after re-evaluating. Other times the refresh leads to a timeout error, but I will try increasing the timeout setting to see if that helps. I have also encountered build errors caused by cljs.user changes, but I will have to keep my eyes out for the specific error message. Thank you for the response 🙇

scaturr15:04:40

@U05224H0W This is the message I get regarding cljs.user

[2023-04-28 15:55:59.829 - WARNING] :shadow.cljs.devtools.server.util/handle-ex - {:msg {:op :cljs-load-sources, :sources [[:shadow.build.npm/resource "node_modules/react/cjs/react.production.min.js"] [:shadow.build.classpath/resource "cljs/user.cljs"]], :call-id 1, :from 12}}
ExceptionInfo no output for id: [:shadow.build.classpath/resource "cljs/user.cljs"] {:resource-id [:shadow.build.classpath/resource "cljs/user.cljs"]}
        shadow.build.data/get-output! (data.clj:202)
        shadow.build.data/get-output! (data.clj:198)
        shadow.cljs.devtools.server.worker.impl/eval17578/fn--17581/fn--17584 (impl.clj:756)
        clojure.core/map/fn--5935 (core.clj:2770)
        clojure.lang.LazySeq.sval (LazySeq.java:42)
        clojure.lang.LazySeq.seq (LazySeq.java:51)
        clojure.lang.RT.seq (RT.java:535)
        clojure.core/seq--5467 (core.clj:139)
        clojure.core.protocols/seq-reduce (protocols.clj:24)
        clojure.core.protocols/fn--8236 (protocols.clj:75)
        clojure.core.protocols/fn--8236 (protocols.clj:75)
        clojure.core.protocols/fn--8178/G--8173--8191 (protocols.clj:13) 

thheller18:04:19

which version do you use? I fixed a related error a while ago, so this shouldn't show up anymore?

scaturr18:04:20

facepalm - it does look like I am a bit behind. Using 2.20.5. I’ll try upgrading.

scaturr14:05:49

@U05224H0W I am up to date on my shadow version, and I am seeing the following error (often after refreshing the browser)

[2023-05-09 14:48:16.223 - WARNING] :shadow.cljs.devtools.server.util/handle-ex - {:msg {:op :cljs-load-sources, :sources [[:shadow.build.npm/resource "node_modules/react/cjs/react.production.min.js"] [:shadow.build.classpath/resource "cljs/user.cljs"]], :call-id 5, :from 51}}
ExceptionInfo no output for id: [:shadow.build.classpath/resource "cljs/user.cljs"] {:resource-id [:shadow.build.classpath/resource "cljs/user.cljs"]}

scaturr14:05:34

This generally appears after I refresh the browser and try to evaluate my app ns again

thheller15:05:51

are you certain you are on the latest version? it is not uncommon that people think they are by updating package.json but then either not actually installing it, or by using a different version in project.clj/deps.edn?

scaturr15:05:34

I don’t know how many more facepalm ’s I am capable of. You are a saint. I had my package.json updated but not my deps.edn

scaturr15:05:40

Trying. Thank you so much 🙇