Interesting find. If it works for you, try jacking in to the project as a shadow-cljs project type. (It’s unclear if you do it this way already, but anyway.)

No

I’ve jacked in as deps.edn + shadow

if I jack in just as shadow there are other issues

What issues? 😃

Well, this template has some deps defined in deps.edn and those don’t get found so the app isn’t compiled consequently

This doesn’t relate to Calva directly

Show us the shadow-cljs.edn file if you can, maybe I can see what’s lacking.

{:deps   true

 :nrepl {:port 8777}

 :builds {:app {:target          :browser
                :output-dir      "resources/public/js/compiled"
                :asset-path      "/js/compiled"
                :modules         {:app {:init-fn craftybones.re-frame-test.core/init
                                        :preloads [devtools.preload]}}
                :devtools        {:http-root    "resources/public"
                                  :http-port    8280
                                  }}}}

Are the deps you need in some alias in deps.edn?

and the deps.edn as follows:

{:paths ["src" "resources"]
 :deps {org.clojure/clojure #:mvn{:version "1.10.1"}
        org.clojure/clojurescript
        {:exclusions [com.google.javascript/closure-compiler-unshaded
                      org.clojure/google-closure-library
                      org.clojure/google-closure-library-third-party]
         :mvn/version "1.10.597"}
        seancorfield/clj-new {:mvn/version "1.0.199"}
        re-com #:mvn{:version "2.7.0"}
        re-frame #:mvn{:version "0.11.0"}
        reagent #:mvn{:version "0.9.1"}
        thheller/shadow-cljs #:mvn{:version "2.8.96"}}
 :aliases
 {:dev {:extra-deps {binaryage/devtools #:mvn{:version "1.0.0"}
                     day8.re-frame/re-frame-10x #:mvn{:version "0.5.1"}
                     day8.re-frame/tracing #:mvn{:version "0.5.3"}}
        :extra-paths ["src" "dev"]}}

Yes, they are

Then instead of :deps true do :deps {:aliases [:dev]}

The way this works is that shadow-cljs will use clojure to start the project. And it needs to know which aliases to activate.

Right. Trying

Worked!

Thanks

so, now if I need to shift aliases, I’d have to go change it in shadow-cljs.edn

Yes, that’s the downside, but usually I find you don’t need to shift such things often. You can also run the deps project and the shadow project in separate vs code windows. That has another issue, but there also seems to be a workaround for that: https://github.com/BetterThanTomorrow/calva/issues/1313

Can I run shadow-cljs from command line and just plugin the repl from Calva instead? So don’t jack in basically but just connect to a running repl?

A small cost to pay I suppose. So far, I’m a little irritated with shadow. A lot of setup as opposed to figwheel

Yes, you can do that as well. If you copy the command that Calva uses for jack-in and then adapt it so that you inject the aliases there, that should work.

I find shadow setup to be far easier than figwheel, but I guess it is a matter of taste as well.

Do you know if there’s an easy way of setting up multiple entry points in shadow? Something like extra-mains in figwheel?

Not familiar with extra-mains. My Figwheel days are way back. 😀