👋 Does shadow require that “clojure tools” (i.e. the clojure script) be installed?

Hi ! is there a way to explicitly ignore specific warnings for specific namespaces without using warnings-as-errors?

Suddenly I am seeing errors from shadow:

[2022-04-07 22:51:42.126 - WARNING] :shadow.cljs.devtools.server.worker.impl/cljs-compile-ex - {:input {:code "(clojure.core/refer-clojure)", :ns app.wallet, :repl true}}
ExceptionInfo Failed to process REPL command {:eof? false, :ns app.wallet, :form (clojure.core/refer-clojure), :source "(clojure.core/refer-clojure)", :tag :shadow.cljs.repl/process-ex}
        shadow.cljs.repl/process-read-result (repl.clj:502)
        shadow.cljs.repl/process-read-result (repl.clj:476)
        shadow.cljs.repl/process-input (repl.clj:661)
        shadow.cljs.repl/process-input (repl.clj:639)
        shadow.cljs.devtools.server.worker.impl/fn--14599 (impl.clj:698)
        shadow.cljs.devtools.server.worker.impl/fn--14599 (impl.clj:688)
        clojure.lang.MultiFn.invoke (MultiFn.java:234)
        shadow.cljs.devtools.server.util/server-thread/fn--14273/fn--14274/fn--14282 (util.clj:269)
        shadow.cljs.devtools.server.util/server-thread/fn--14273/fn--14274 (util.clj:268)
        shadow.cljs.devtools.server.util/server-thread/fn--14273 (util.clj:241)
        java.lang.Thread.run (Thread.java:829)
Caused by:
ExceptionInfo ns* not supported (require, require-macros, import, import-macros, ... must be part of your ns form) {:rename-macros nil, :renames {}, :use-macros nil, :excludes #{}, :name app.wallet, :op :ns*, :env {:fn-scope [], :locals {}, :js-globals {console {:op :js-var, :name console, :ns js}, location {:op :js-var, :name location, :ns js}, escape {:op :js-var, :name escape, :ns js}, screen {:op :js-var, :name screen, :ns js}, global {:op :js-var, :name global, :ns js}, process {:op :js-var, :name process, :ns js}, require {:op :js-var, :name require, :ns js}, alert {:op :js-var, :name alert, :ns js}, history {:op :js-var, :name history, :ns js}, window {:op :js-var, :name window, :ns js}, module {:op :js-var, :name module, :ns js}, exports {:op :js-var, :name exports, :ns js}, document {:op :js-var, :name document, :ns js}, navigator {:op :js-var, :name navigator, :ns js}, unescape {:op :js-var, :name unescape, :ns js}}, :ns {:rename-macros nil, :renames {}, :meta {:file "app/wallet.cljs", :line 1, :column 5, :end-line 1, :end-column 15}, :ns-aliases {cljs.loader shadow.loader, react shadow.js.shim.module$react, clojure.pprint cljs.pprint, clojure.spec.alpha cljs.spec.alpha}, :use-macros nil, :excludes #{}, :shadow/js-access-properties #{"Text"}, :name app.wallet, :reader-aliases {}, :js-aliases {"react-native" shadow.js.shim.module$react_native}, :imports nil, :requires {cljs.core cljs.core, goog goog, shadow.js.shim.module$react_native shadow.js.shim.module$react_native, rn shadow.js.shim.module$react_native}, :seen #{:require}, :uses nil, :defs {wallet-tab {:protocol-inline nil, :meta {:file "app/wallet.cljs", :line 5, :column 7, :end-line 5, :end-column 17, :arglists (quote ([]))}, :name app.wallet/wallet-tab, :file "app/wallet.cljs", :end-column 17, :method-params ([]), :protocol-impl nil, :arglists-meta (nil nil), :column 1, :variadic? false, :line 5, :ret-tag cljs.core/IVector, :end-line 5, :max-fixed-arity 0, :fn-var true, :arglists (quote ([]))}}, :require-macros {cljs.core cljs.core}, :cljs.analyzer/constants {:seen #{:>}, :order [:>]}, :flags {:require #{}}, :js-deps {"react-native" {:as rn}}, :deps [goog cljs.core shadow.js.shim.module$react_native]}, :def-emits-var true, :shadow.build/mode :dev, :column 1, :shadow.build/tweaks false, :line 1, :shadow.build.compiler/repl-context true, :context :expr}, :imports nil, :requires nil, :uses nil, :reload {:use nil, :require nil, :use-macros nil, :require-macros nil}, :require-macros nil, :form (ns* (:refer-clojure)), :reloads {}, :deps []}
        shadow.build.compiler/post-analyze (compiler.clj:94)
        shadow.build.compiler/post-analyze (compiler.clj:89)
        shadow.build.compiler/analyze/fn--12392 (compiler.clj:265)
        shadow.build.compiler/analyze (compiler.clj:252)
        shadow.build.compiler/analyze (compiler.clj:211)
        shadow.cljs.repl/repl-compile/fn--14080/fn--14081 (repl.clj:441)
        shadow.cljs.repl/repl-compile/fn--14080 (repl.clj:414)
        shadow.cljs.repl/repl-compile (repl.clj:412)
        shadow.cljs.repl/repl-compile (repl.clj:409)
        shadow.cljs.repl/process-read-result (repl.clj:500)
        shadow.cljs.repl/process-read-result (repl.clj:476)

Evaluating (refer-clojure) throws an error in shadow-cljs and also prints a huge map

{:rename-macros nil, :renames {}, :use-macros nil, :excludes #{}, :name calva.fmt.formatter, :op :ns*, :env {:fn-scope [], :locals {}, :js-globals {console {...

Question about reloading and component-local state. I've set up Shadow to reload my code using https://github.com/pesterhazy/shadow-jest/blob/tictactoe/src/main/tdd/main.cljs#L5, which works fine. However, I'm seeing that component-local state gets lost. My code uses React's useState (here's a https://github.com/pesterhazy/shadow-jest/blob/tictactoe/src/main/tdd/domain/board.cljs#L9 to the code). From reagent I'm used to defonce'd state atoms, which would preserve inputs. This is very useful because while debugging/applying styles I don't need to manually recreate state every time I change a file. Now after moving to modern React and useState, is there a way to both • rerender the components after reload to let the new code take effect and • preserve the component-local state?

this is not something shadow-cljs is involved in really. it is either react or reagent. they manage the state, shadow-cljs just calls a function

generally I would say that local state is always lost

I don't know how react-refresh handles preserving useState but it seemed quite involved and required support from the compiler

I didn't know about react-refresh, that's an interesting pointer, thanks!

I knew that my question wasn't strictly about shadow-cljs, but given that it does reloading so well this channel felt like a good place to ask

well yeah if you wanted something like react-refresh then shadow-cljs would need to get more involved. I can't really figure out what it would need to do though. likely some compiler modifications that would get icky 😛

I used another approach for now. I created a "playground" part of the app, which has data pre-filled in. So I can use that to edit styles

This kind of stuff mostly just worked with reagent/re-frame's global state atom. I didn't realize this was such a big advantage of the (otherwise icky) global var

Not sure if you’ve looked into devcards. My favorite dev experience was using bruce’s test runner in one tab, the devcards in another tab, and the “real” tab in a third. Multiple entries on a build to enable all of this was a really great experience

Yeah, really love devcards as well. For now, I'm keeping it simple with a https://github.com/pesterhazy/shadow-jest/blob/tictactoe/src/main/tdd/main.cljs#L12

While writing this I discovered that shadow-cljs's dev webserver uses a trick to serve index.html back to arbitrary urls but only when used as the entry point - not for images, css etc. I was confused as to how this could possibly work. Turns out it checks if "text/html" is https://github.com/thheller/shadow-cljs/blob/ba0a02aec050c6bc8db1932916009400f99d3cce/src/main/shadow/http/push_state.clj#L12. Ingenious approach that I haven't seen elsewhere

The benefit is that you still get nice 404 if you mistype a jpg url in your code (whereas other popular ad-hoc webservers just blindly serve you index.html for any route that's not found)