Clojurians Log v2

You can have a run configuration to run npm run. It's what I'm using at the moment.

After adding :repl-init-ns option to my shadow-cljs.edn, I’ve been encountering the following error after leaving my browser repl idle:

[2021-01-05 13:26:03.677 - WARNING] :shadow.cljs.devtools.server.worker.impl/cljs-compile-ex - {:input {:code "(test-client)", :ns client, :repl true}}
ExceptionInfo Failed to process REPL command {:eof? false, :ns client, :form (test-client), :source "(test-client)", :tag :shadow.cljs.repl/process-ex}
        shadow.cljs.repl/process-read-result (repl.clj:524)
        shadow.cljs.repl/process-read-result (repl.clj:498)
        shadow.cljs.repl/process-input (repl.clj:682)
        shadow.cljs.repl/process-input (repl.clj:660)
        shadow.cljs.devtools.server.worker.impl/fn--15170 (impl.clj:755)
        shadow.cljs.devtools.server.worker.impl/fn--15170 (impl.clj:745)
        clojure.lang.MultiFn.invoke (MultiFn.java:234)
        shadow.cljs.devtools.server.util/server-thread/fn--14833/fn--14834/fn--14842 (util.clj:285)
        shadow.cljs.devtools.server.util/server-thread/fn--14833/fn--14834 (util.clj:284)
        shadow.cljs.devtools.server.util/server-thread/fn--14833 (util.clj:257)
        java.lang.Thread.run (Thread.java:834)
Caused by:
ExceptionInfo no source by provide: client {:provide client}
        shadow.build.data/get-source-id-by-provide (data.clj:187)
        shadow.build.data/get-source-id-by-provide (data.clj:184)
        shadow.build.data/get-source-by-provide (data.clj:190)
        shadow.build.data/get-source-by-provide (data.clj:189)
        shadow.cljs.repl/repl-compile/fn--14400/fn--14401 (repl.clj:460)

(ns client
  (:require [cljs.repl :refer [doc find-doc source apropos pst dir]]
            [re-frame.core :as rf]
            [re-frame.db :as rfdb]))

(defn test-client []
  {:status "alive"})

(defn db []
  @rfdb/app-db)

Can I get Shadow to reload and re-run tests (`:target :node-test`) when a non-clojure file changes (in this case an edn file with expected results)?

@thheller I'm sorry for notifying you directly, but I think that you're the only who can answer this question. In the project I'm working on we're using following strategy to resolve lazy modules:

(defn- lazy-resolve
  [symbol-k]
  (let [symbol' (symbol symbol-k)
        module' (-> (str symbol')
                    (s/replace #"/.*" "")
                    (s/split #"\.")
                    ((partial s/join "-"))
                    keyword)]
    `(conj [] ~module' (cond-> (fn [] (resolve (quote ~symbol')))
                         config.core/DEV?
                         (with-meta {:sym (quote ~symbol')})))))

@karol.wojcik look at a build report to see where the size is coming from https://shadow-cljs.github.io/docs/UsersGuide.html#build-report

in general you should avoid resolve. there is also https://clojureverse.org/t/shadow-lazy-convenience-wrapper-for-shadow-loader-cljs-loader/3841

@thheller I'm using code splitting and lazy modules. I'm trying to say that requiring lazy different modules to main bundle results in those long strings of resolves. I would like to make it smaller.

@thheller Ok got it. Will use loadable and the issue is resolved. 🙂 Thank you so much!

as I said ... look at the build report so you can figure out WHY you get the 200kb

my hunch would be that you are importing cljs.analyzer somewhere maybe

@thheller i got a lot of lazy calls, and a lot of lazy modules. Anyway thanks for hint with cljs.analyzer. Will check this out

that doesn't tell me anything. I do not know what a lazy call or lazy module is in your terms

I know what it is in the case of shadow.lazy but if you build your own I do not know what that does

I boiled down to two problems. • Referencing deprecated functions (and multi-method)

(defn ^:deprecated my-fn [a b] (+ a b))

(def a 1)
(def a 2)

How do I control what browser the browser-repl connects to?

@grounded_sage by default it’s the first one that connects, but you can change it to be the last with :repl {:runtime-select :latest} in shadow-cljs.edn

I mean that I'm having 30-40 modules (you told me once that I should group those modules together (will do it as well)) in :modules section in shadow-cljs.edn configuration which I use quite extensively in main module. The strategy of requiring the module is combination of shadow.loader + resolve. Resolve is the function which adds that 200kb to main bundle. Checked whether cljs.analyzer is imported somewhere, but it's not 🙂

Thank you very much for the respnse. Will use Loadable to get rid of resolve 🙂

resolve adds a bunch of boilerplate "noise" yes. didn't expect it to get to 200kb though.

there is also now (shadow/repl :app {:runtime-id 123})

@marques.goncalves.fel your question is unclear. need more information about what you are doing. how do you "eval" the dev ns? (require 'dev) in the REPL? load-file from the editor? (ns dev)? if you just use (dev/whatever) without doing those first you'll get the dev is not defined error?

I eval the file using cider-eval-buffer. The file in question is the dev.cljs which contains the dev namespace.

and what is in that file?

Lot of stuff! Hahahaha. But I found out that it didn't load when it referred another namespace that contained a deprecated function like this: (defn ^:deprecated ab [a b] (+ a b) Or when the namespace itself defined a value two times, like this:

(def company-id (random-uuid))
; Some other code
(def company-id #uuid "0acf9013-7c42-49fc-ae4b-221639bf9a34")

Thanks @mkvlr that is exactly what I needed.

Is this documented somewhere and how you use it?

ah so whenever there is a warning

what do you mean? thats all there is to it?

Sorry I am just unsure how :runtime-id works. Where is it generated? I don’t see anything that says runtime id when I run shadow-cljs watch app etc. I haven’t been that deep in shadow-cljs lately or doing any complex configurations.

ah sorry. it is visible in the ui http://localhost:9630/runtimes

or listed in most runtimes on connect

browser.cljs:20 shadow-cljs: #13 ready! or so

13 would be the runtime-id

🙏

Yes, I think so.

right yeah I changed it that warnings in compiled code prevent the code from being loaded

still need to add an option to turn that off

Got it! Cool! Thanks for the information. Do you think that this is an issue that a new comer to the repo would be able to do? Maybe I can try to add this option.

fixed in 2.11.14 via :devtools {:ignore-warnings true} in your build config

cool! Thanks!