Fork me on GitHub
#calva
<
2021-02-03
>
pez12:02:42

New release announced. Please visit #announcements and cheer it on with emojis and replies. 😃

🙌 6
❤️ 3
pez12:02:55

And if you find typos and stuff in the announcement article, please let me know. Written in a bit of too much hurry. ❤️

flowthing12:02:24

You guys ship features at a breakneck speed. Kudos!

metal 6
❤️ 6
Aleksander Rendtslev15:02:12

I’m trying to run the deps.edn + shadow.cljs command, but the cljs part keeps failing with the following:

clj꞉user꞉> 
; Creating cljs repl session...
; Connecting cljs repl: deps.edn + shadow-cljs...
;   The Calva Connection Log might have more connection progress information.
; Execution error (ClassNotFoundException) at java.net.URLClassLoader/findClass (URLClassLoader.java:471).
shadow.cljs.devtools.api
Any clues? (I’m back to trying to make Calva be my daily driver. For some reason, writing clojure is a lot smoother for me in VSCode than Emacs)

gabo16:02:22

Hi there. Can you share your deps.edn ? I think you have to add an alias for shadow. I use it like this:

:aliases
 { :ui
  {:extra-deps {thheller/shadow-cljs {:mvn/version "2.11.15"}}}

  :watch
  {:main-opts ["-m" "shadow.cljs.devtools.cli"
               "watch" ":frontend"]}
And select those aliases when prompted by calva

gabo16:02:37

(if you have shadow-clj on your main deps you could omit the ui alias)

gabo17:02:17

You're welcome 😄

pez17:02:53

Thank you @U014B62SC3V!

😄 3
Aleksander Rendtslev17:02:29

@pez this works perfectly with Fulcro. It allows for evaluating both client and server side with output in the same repl window. So we could update the Calva documentation accordingly

👍 3
pez17:02:27

So awesome! We should have a page on http://calva.io about that as well.

bringe18:02:36

I agree. @U01DH13SK8E A doc addition to explain usage with Fulcro would be great!

bringe18:02:22

Maybe an update to this section: https://calva.io/jack-in-guide/#about-full-stack-applications And then a new page like "Using Calva with Fuclro" might be good, to go under the "Using Calva with X" section.

pez16:02:06

Hopefully it is a general solution for deps.edn + shadow-cljs

n2o16:02:12

Hm, I’m getting this error message when I try this approach with my fullstack Clojure / ClojureScript plugin with shadow-cljs and re-frame:

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

n2o16:02:48

The REPL is available, but building my cljs project failed. Any ideas on this? :thinking_face: Thanks 🙂

pez16:02:37

Can you share your configs? (I think it might be wise to continue this in a new thread. This one might go down Slack’s memory hole at any time now.

Marian01:02:50

@U1PCFQUR3 Have you found the problem? I’m trying to setup clojurescript in clojure project and I get similar ClassNotFoundException com/google/common/collect/Streams

n2o21:02:15

Jep, manually add the Guava library to your project.

seancorfield18:02:41

@pez given that I installed that .vsix file you linked to, in order to test the hide REPL UI setting, will that Calva install auto-update to new releases as they become available?

seancorfield18:02:46

(I just fired up VS Code on my Windows/WSL2 laptop and I see it has already sync'd the Calva extension and settings from my Mac desktop -- which always pleases me about VS Code 🙂 )

seancorfield18:02:22

Hmm, looks like 2.0.158 is what is installed on my laptop so the answer is "yes" -- and my Mac install just needed a reload to pick up that version too. Slick.

pez18:02:35

@seancorfield VS Code is pretty awesome with the updates and settings sync. 😃 We version our test VSIX builds such they should play together with the auto-update when we make releases. NB: You will probably need to set your options for hiding the REPL UI again, because I renamed it.

seancorfield19:02:46

Thanks. Done. cmd-, and type hide. VS Code makes finding this stuff so easy!

pez19:02:05

We should hint a bit about this at http://calva.io. People coming from other editors often bring expectations that makes it easy to miss how easy some things are in vscode. 😀

seancorfield19:02:35

I have to be honest, I continue to be pleasantly surprised by VS Code, almost on a daily basis... The WSL2 integration on Windows is phenomenal and having the same key bindings and behavior automatically sync'd back and forth between my Mac desktop and my Windows laptop is so much more seamless than what I was used to with Atom (for the previous four or five years!).

seancorfield19:02:44

And with us being all-in with Atlassian products at work, I love the Jira/BitBucket integration -- and some of my colleagues are getting jealous that I pretty much never have to visit http://atlassian.net: I can do all the ticket/pull request stuff inside VS Code 🙂

😀 3
afry18:02:37

Hey @pez @brandon.ringe, did you guys do a release recently? I think the slurping/barfing key commands aren't working. Just fyi 👼 . I get more comfortable with Calva by the day, and I like it!

bringe18:02:30

These have been changed recently, check the keybindings in vs code simple_smile

bringe18:02:59

There was an info popup about it when the new version first ran - or should have been at least. It only appears once, informing that some keybindings changed.

bringe18:02:55

Just a bit of retraining the fingers/brain. The previous slurp/barf shortcuts overrode what some people expect to be navigation shortcuts. Also, ctrl+w now closes tabs as many might expect, instead of expanding the selection (now that's shift+alt+rightArrow

afry18:02:25

Awesome, thanks

👍 3
pez18:02:33

Changing the bindings back to what you are used to is what I would recommend, @andyfry01.

clyfe19:02:16

Short update on lsp/kondo memory spike (long thread in lsp): we can introduce some conf in Calva - and folks with low memory can toggle it, such that lsp runs with less memory but takes longer to init a project (just first run until caches are build, it's fast after). This can placate the folks that see freezes and such.

bringe19:02:27

I think the setting would exist in the lsp conf, but yeah, if we can verify that that works, it may be a good option, at least temporarily.