Fork me on GitHub
Baibhav Bista05:02:16

Hello everyone, I have been having a problem with the "show hover" you see when hovering over a function name when aliasing. I'm asking here to know if there are some things I need to set up or if this is a known issue in calva Edit: Solution: Reloading VS Code and jacking in again fixed the problem for me.

Baibhav Bista05:02:46

if I use the non-aliased name, the hover works

Baibhav Bista05:02:25

however, the following does not show the hover

Baibhav Bista05:02:29

I'm running Lein + CLJS + Figwheel on WSL2 and am jacked in. Everything else is working correctly.


JS lookups are a bit erratic. I haven’t quite figured out a pattern to it.

Baibhav Bista08:02:13

@U0ETXRFEW after you said that it was erratic I closed and reopened Vs-code, and jacked-in, and now it seems to work XD I don't know what the problem was but a reload fixed things for me


Funny. I should try restart as well, maybe. 😃


I have a basic shadow-cljs + deps.edn setup that won't jack in.

; Execution error (ClassNotFoundException) at (
; Error while connecting cljs REPL: TypeError: Cannot read property 'search' of undefined
There's a resolved git issue here: that's similar in nature. Could it be connected to that? I was actually trying to follow the basic Fulcro tutorial when this happened.


There is also a new issue filed about it. (And in fact there was someone in this channel that reported success with Fulcro fullstack the other day…)


This one, is the one I was remembering.


Thanks! That works swimmingly!


Oh, that’s awesome to know!


Welcome, @n2o!


hey, thanks for pointing me to this channel 🙂 i’ll give the solution you suggested in the issue a try this evening :thumbsup:

metal 1

See my post right above your entry announcement for a link to the thread where the solution was posted.

👍 1
🚀 1

Full Stack Clojure: Clojure backend with shadow-cljs compiled frontend (re-frame): I am having an issue same as seen here: But the workaround does not properly work in my environment. When I try to start a REPL, I get this error:

shadow-cljs - HTTP server available at 
shadow-cljs - server version: 2.11.18 running at 
shadow-cljs - nREPL server started on port 8777
shadow-cljs - watching build :app
[:app] Configuring build.
[:app] Compiling ...
[2021-02-15 17:26:16.000 - WARNING] :shadow.cljs.devtools.server.util/handle-ex - {:msg {:type :start-autobuild}}
NoClassDefFoundError com/google/common/collect/Streams


My deps.edn looks like this

{:paths ["src/main" "src/test"]
 :aliases {:watch
           {:main-opts ["-m" "shadow.cljs.devtools.cli"
                        "watch" ":app"]}
           {:extra-deps {com.datomic/dev-local {:local/root "local_jars/dev-local/dev-local.jar"}}}}}
and my shadow-cljs.edn like this:
{:deps true
 :nrepl {:port 8777}
 :builds {:app {:target :browser
                :modules [...]
                :output-dir "resources/public/js/compiled"
                :asset-path "/js/compiled"
                :dev {:compiler-options {:closure-defines {re-frame.trace.trace-enabled? true}}}
                :release [...]
                :devtools {:http-root "resources/public"
                           :http-port 8700
                           :preloads [devtools.preload]}}}}


When I then try to start a REPL via Calva, using deps.edn, then starting with the aliases :watch and dev-local, results in the error above. Looks like some deps from Google, which should come with the Closure Compiler Collection are not in my classpath…? :thinking_face:


The full stacktrace looks like this:

NoClassDefFoundError com/google/common/collect/Streams$Require.asSymbolList ($Base.getRequiredSymbols ( ( ( ( ($parseForCompilation$4 ( ( ( ( (
        jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (
Caused by:
        jdk.internal.loader.BuiltinClassLoader.loadClass (
        jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass (
        java.lang.ClassLoader.loadClass ($Require.asSymbolList ($Base.getRequiredSymbols (


Does anyone have any ideas on this problem? Would great to solve this 🙂 Essentially, this is a re-frame project with deps.edn and a backend written in Clojure, starting an http server as an API.


I don’t see shadow-cljs in the dependencies of your deps.edn. Could that be the problem?


Nope, of course it is in my configuration, I just did not want to spam that lot 😉 here are some of my deps, the list is quite long in the original project

{:paths ["src/main" "src/test"]
 :deps {[...]
        org.clojure/clojure {:mvn/version "1.10.2"}
        org.clojure/clojurescript {:mvn/version "1.10.773"}
        re-frame/re-frame {:mvn/version "1.1.2"}
        reagent/reagent {:mvn/version "1.0.0"}
        ring-cors/ring-cors {:mvn/version "0.1.13"}
        ring-middleware-format/ring-middleware-format {:mvn/version "0.7.4"}
        ring/ring-mock {:mvn/version "0.4.0"}
        ring/ring {:mvn/version "1.9.0"}
        ring/ring-defaults {:mvn/version "0.3.2"}
        thheller/shadow-cljs {:mvn/version "2.11.18"}}
 :aliases {:watch
           {:main-opts ["-m" "shadow.cljs.devtools.cli"
                        "watch" ":app"]}
           {:extra-deps {com.datomic/dev-local {:local/root "local_jars/dev-local/dev-local.jar"}}}}}


When I use the workaround described in your docs to use two separate workspaces, the project works as expected (except for the fact that I have to use two windows, but that is still better than messing around with Cursive)


maybe I build a minimal example tomorrow and paste it in the github issue and this thread, so that you can better see it on your machine. Remote debugging can be very difficult 🙂


Indeed. A minimal example will be super!


Hm… My minimal example works as expected and as described with your solution above… I used my own project and removed everything which is not crucial for the example… Well… Now I have to search the root of the problem 😬


That’s the wonderful thing with minimal examples. Haha.


Super happy it works! We should as a minimum document the way to do this. But I also think maybe we can build it in to the deps.edn + shadow-cljs connect sequence….


New version of the standalone REPL PR for you to test, friends. I changed the name of the command to Fire up a “Getting Started” REPL, and tried to make it more of that, by adding a Paredit starter file and also a (yet unfinished) Clojure basics guide. I’m thinking it can be a pretty nice way to start your Clojure journey: Fire up a REPL, evaluate and experiment with some code in some well thought through order (hoping I can achieve that, of course). I’m a bit unsure about the actual terminology, I don’t want it to get too formal, but don’t want to lie either… Please help test the basic functionality and also test the guides. Probably lots of spelling errors and such there… Here’s the VSIX:

hyper-clap 1
calva 2
catjam 2

Ran into some problems out of the gate:

java -jar c:\Users\[REDACTED]\.vscode\extensions\betterthantomorrow.calva-2.0.173-814-connect-without-project-7ab7b6e8\deps.clj.jar -Sdeps "{:deps {nrepl/nrepl {:mvn/version,""0.8.3""},cider/cider-nrepl {:mvn/version,""0.25.8""}}}"  -m nrepl.cmdline --middleware "[cider.nrepl/cider-middleware]"
Could not find C:\Users\[REDACTED]\.deps.clj\\ClojureTools\clojure-tools-
Attempting download from 
Error building classpath. class java.lang.Character cannot be cast to class java.util.Map$Entry (java.lang.Character and java.util.Map$Entry are in module java.base of loader 'bootstrap')
java.lang.ClassCastException: class java.lang.Character cannot be cast to class java.util.Map$Entry (java.lang.Character and java.util.Map$Entry are in module java.base of loader 'bootstrap')
        at clojure.core$key.invokeStatic(core.clj:1567)
        at clojure.core$merge_with$merge_entry__5962.invoke(core.clj:3060)
        at clojure.core$reduce1.invokeStatic(core.clj:944)
        at clojure.core$merge_with$merge2__5964.invoke(core.clj:3066)
        at clojure.lang.ArrayChunk.reduce(
        at clojure.core$reduce1.invokeStatic(core.clj:942)
        at clojure.core$reduce1.invokeStatic(core.clj:934)
        at clojure.core$merge_with.invokeStatic(core.clj:3059)
        at clojure.core$merge_with.doInvoke(core.clj:3051)
        at clojure.lang.RestFn.applyTo(
        at clojure.core$apply.invokeStatic(core.clj:667)
        at clojure.core$apply.invoke(core.clj:660)
        at clojure.lang.RestFn.applyTo(
        at clojure.lang.Var.applyTo(
        at clojure.core$apply.invokeStatic(core.clj:665)
        at clojure.main$main_opt.invokeStatic(main.clj:514)
        at clojure.main$main_opt.invoke(main.clj:510)
        at clojure.main$main.invokeStatic(main.clj:664)
        at clojure.main$main.doInvoke(main.clj:616)
        at clojure.lang.RestFn.applyTo(
        at clojure.lang.Var.applyTo(
        at clojure.main.main(
Jack-in process exited. Status: 1
System configuration:
Version: 1.53.1 (user setup)
Commit: 5d424b828ada08e1eb9f95d6cb41120234ef57c7
Date: 2021-02-08T23:29:42.785Z
Electron: 11.2.1
Chrome: 87.0.4280.141
Node.js: 12.18.3
OS: Windows_NT x64 10.0.21313


This was invoked using the "Fire up a 'Getting Started' REPL" in a new Code Window, so with a new workspace and no existing project.


Interesting. What's your JDK version?


❯ java -version
openjdk version "15.0.1" 2020-10-20
OpenJDK Runtime Environment AdoptOpenJDK (build 15.0.1+9)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 15.0.1+9, mixed mode, sharing)


This version of Calva is working in a workspace where I already have projects, so it's possible that it is brought on because it was a new workspace without predefined projects. Uncertain about that.


Thanks for helping out testing! It looks like the error @UUDGHH2J1 ran into as well yesterday. Probably to do with that your username contains a space or two. I'm guessing your other projects are not using deps.edn, because this fails with the currently released Calva as well.


@U0ETXRFEW, no space in my user name. 😕 But you are correct about not using deps.edn. The other projects I have right now are Lein based.


No spaces, huh? Not good. Then the problem is deeper. We have a long sad story with quoting the jack-in command line on Windows...


@U0ETXRFEW, yeah, I think I ran into that trying to get Reveal to work. We eventually figured out the escaping which allowed me to modify jvm-opts for reveal, but it wasn't pleasant. This could be because you're using cmd.exe to launch? PowerShell is probably better for Windows users and your sanity anyway. VS Code suggests that it requires Windows 7. PowerShell 2 is integrated for Windows 7. So at a minimum, you should be able to rely on leveraging PowerShell to begin processes and it would likely


I’ve been using powershell and new powershell and everything. Always some Windows setup that doesn’t work. I thought I had nailed it this time, since it worked for all Windows testers.


The good part here is that I can reproduce the error on my VirtualBox Windows.


And I can still jack in to a deps.edn project, so it’s not clearcut a quoting problem…