This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-17
Channels
- # announcements (1)
- # babashka (94)
- # beginners (76)
- # calva (24)
- # cider (24)
- # clj-kondo (1)
- # cljs-dev (16)
- # cljsrn (45)
- # clojure (135)
- # clojure-europe (9)
- # clojure-france (5)
- # clojure-germany (2)
- # clojure-italy (12)
- # clojure-losangeles (13)
- # clojure-nl (3)
- # clojure-portugal (54)
- # clojure-uk (20)
- # clojurescript (55)
- # conjure (67)
- # core-async (5)
- # cursive (2)
- # datomic (10)
- # docker (7)
- # duct (22)
- # emacs (16)
- # fulcro (34)
- # graalvm (15)
- # hoplon (1)
- # instaparse (1)
- # jobs-discuss (3)
- # juxt (94)
- # luminus (1)
- # meander (4)
- # off-topic (13)
- # pathom (4)
- # pedestal (1)
- # ring (3)
- # ring-swagger (2)
- # shadow-cljs (61)
- # spacemacs (17)
- # specter (2)
- # sql (23)
- # xtdb (33)
Hi all, anyone had any luck getting `shadow-cljs`, `deps.edn` and `cider` working nicely together?
Things work perfectly just using `shadow-cljs` and `cider` but when I try to use `deps.edn` as well the `cider-jack-in-cljs` stops working.
I select `cider-jack-in-cljs` -> `clojure-cli` and then my build and I get the following error.
error in process filter: The shadow-cljs ClojureScript REPL is not available. Please check
looks related to this https://github.com/clojure-emacs/cider/issues/2812?
Currently there is no way to get the cljs repl with shadow out of the box if you you use deps.edn or lein. You need to launch it yourself.
But the error you are getting looks like there is already something in your setup that is amiss.
does this work from the command line? its complaining that shadow isn't on the classpath which sounds like what you are attempting won't be able to work. are you missing shadow as a dependency in deps.edn?
it does work from the command line, I had it in my deps.edn but under an alias as was shown in the shadow docs, but yeah that was that problem I will try your solution @UL638RXE2
Hello, did you try to launch a shadow-CLJS watch app, and then cider-connect-cljs,
It works fine for me.
When running tests from Cider, Cider is not aware of Leiningen :test
profile resource-paths
, is there a workaround?
Maybe best to put the resources under dev and test profiles, and not in uberjar’s resources
@erwinrooijakkers You can adjust the command CIDER uses to run leiningen to include the :test
profile as well.
Thanks
See https://metaredux.com/posts/2019/11/02/hard-cider-understanding-the-jack-in-process.html
I think best practice is to put the resources under :dev
https://github.com/technomancy/leiningen/blob/master/doc/PROFILES.md#task-specific-profiles
Hey @bozhidar would you be open to a PR that adds babashka support as a project type? Now that babashka ships with an nRepl server, it'd be awesome to be able to quickly get into a babashka compatable scripting environment via cider-jack-in
. If you think it's too specific, happy to keep using cider-connect
, but I think it could be really cool!
( @rschmukler there are some docs here, including a script to write a .nrepl-port file on startup, which may help: https://github.com/borkdude/babashka/blob/master/doc/repl.md#nrepl )
@borkdude amazing! I've had good success with cider + bb
. But it'd be awesome to be able to do cider-jack-in
anywhere and get prompted to automatically start a new babashka process w/ --nrepl-server
so that I can just hop into scripting. It's definitely not a huge pain as is, but figured it could be convenient for others