This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-07
Channels
- # babashka (17)
- # beginners (33)
- # calva (9)
- # cider (2)
- # clj-kondo (17)
- # cljs-dev (2)
- # cljsrn (2)
- # clojars (3)
- # clojure (60)
- # clojure-australia (2)
- # clojure-europe (8)
- # clojure-gamedev (5)
- # clojurescript (27)
- # cursive (2)
- # emacs (9)
- # fulcro (8)
- # gratitude (5)
- # lsp (41)
- # malli (3)
- # meander (18)
- # pathom (5)
- # polylith (25)
- # re-frame (17)
- # reagent (1)
- # rewrite-clj (6)
- # shadow-cljs (11)
- # uncomplicate (5)
- # vim (6)
- # web-security (5)
My clojure-lsp process takes quite a bit of memory and occasionally gets very heavy on CPU usage. Is that to be expected? Any practical ways to limit how much resources it uses without compromising its functionality too much?
Not really, it actually uses high CPU/mem only during startup to analyze the project
Has anyone in Vim land had success incorporating the experimental add-libs
from clojure.tools.deps.alpha
into their workflow? I have an alias in my deps.edn that I'm including when I start my iced repl
, and add-libs
is available in my app code, but when I try to require ring and start a jetty server, the server responds only with “empty response” errors until I restart the repl and trigger a proper download of all dependencies.
I'm sure the problem is entirely between my chair and keyboard, but I'm currently blanking on a solution.
This is how I hotload libraries with add-libs, I use Emacs although this approach should be editor agnostics. Make sure the add-libs dependency is being loaded when initially running the REPL process. https://practical.li/clojure/alternative-tools/clojure-tools/hotload-libraries.html