This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-10-16
Channels
- # aleph (73)
- # babashka (12)
- # beginners (17)
- # calva (9)
- # clerk (8)
- # clj-otel (1)
- # clojars (8)
- # clojure (3)
- # clojure-europe (13)
- # clojure-nl (3)
- # clojure-norway (66)
- # clojure-uk (3)
- # clojuredesign-podcast (2)
- # clojurescript (11)
- # clr (8)
- # conjure (2)
- # core-typed (1)
- # data-science (11)
- # datahike (4)
- # etaoin (5)
- # events (1)
- # graalvm (2)
- # honeysql (27)
- # hyperfiddle (26)
- # introduce-yourself (3)
- # lsp (3)
- # membrane (1)
- # off-topic (60)
- # polylith (20)
- # practicalli (4)
- # reitit (3)
- # shadow-cljs (18)
- # specter (2)
- # xtdb (1)
Hi, is it possible define in a project's deps.edn:
{,,,
:aliases {:cider {:extra-deps {cider/cider-nrepl {:mvn/version "0.40.0"}
refactor-nrepl/refactor-nrepl {:mvn/version "3.9.0"}}}}}
And to activate it through shadow-cljs -A:cider watch dev
?
I've tried a few variations and none are working for me. The user manual suggests creating a user-global configuration, that's fine but does not result in a self-contained projectI don't understand the question. yes, aliases can be activated that way. assuming a new jvm is launched for that command
The question is: can I get the cider-nrepl middleware into the classpath so that shadow-cljs will activate the middleware The constraints I'm pursuing are: • cider should be optional • all code should be contained in the repo i.e. don't expect the user to define dotfiles
i.e. shadow-cljs starts ONE jvm, and if other commands run they use that instead of running a new one
https://shadow-cljs.github.io/docs/UsersGuide.html#_server_mode https://code.thheller.com/blog/shadow-cljs/2017/11/18/the-many-ways-to-use-shadow-cljs.html