This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-02-15
Channels
- # announcements (8)
- # architecture (9)
- # autochrome-github (1)
- # babashka (48)
- # beginners (55)
- # calva (36)
- # cider (16)
- # clj-commons (1)
- # clj-kondo (38)
- # cljs-dev (44)
- # cljsrn (1)
- # clojure (164)
- # clojure-europe (35)
- # clojure-nl (2)
- # clojure-norway (10)
- # clojure-uk (23)
- # clojurescript (50)
- # conjure (24)
- # core-async (1)
- # cryogen (2)
- # cursive (38)
- # datalevin (11)
- # datascript (2)
- # datomic (13)
- # duct (1)
- # emacs (16)
- # events (12)
- # exercism (3)
- # figwheel-main (7)
- # fulcro (26)
- # honeysql (5)
- # integrant (1)
- # jobs (3)
- # kaocha (6)
- # lsp (72)
- # malli (22)
- # nextjournal (35)
- # nrepl (1)
- # off-topic (34)
- # pathom (5)
- # polylith (8)
- # portal (40)
- # re-frame (14)
- # reagent (42)
- # reitit (1)
- # releases (1)
- # remote-jobs (1)
- # reveal (9)
- # sci (2)
- # shadow-cljs (13)
- # sql (3)
- # tools-deps (33)
- # vim (25)
How does one install sci
as an external dependency?
I try to run tests of malli
and they fail with this error: :malli.core/sci-not-available
Should I include it into my ~/.clojure/deps.edn
?
This was the info from #babashka channel. But it's not enough context.
How would one run tests from emacs(spacemacs+CIDER)? If I understand correctly you'd need to run it a JS-Clojure REPL. It failed for me when I used Java-Clojure REPL.
@invertisment_clojuria You can place a file .dir-locals
in the repo:
((clojure-mode
(cider-clojure-cli-aliases . "test")))
What should I choose when it says "connect sibling cljs"? There are many options. node
, figwheel
, shadow
and others
Dunno, I don't ever use this. If I want to run tests, I do it directly from the Node REPL
So you develop without a REPL?
I'm used to have everything under one process in Java. That's why I ask. I know that in CLJS it's different.
So should it be ./bin/node
and that's it? And then you'd proceed to go and change the sources?
And have the REPL running just in case?
I do use the REPL, but for CLJS I found it too brittle to do it from my editor so I chose to simplify things. I use (require '[ns] :reload)
in the REPL when I want to reload changes, and invoke test expressions or files when I want to test something. This is a spartan workflow, but it's the least time consuming for me personally.
Should I also add how to start-up the emacs REPL into the README? I'll make a PR for a bugfix.
I was just providing info, I'm not the maintainer of this project, so I'll let @ikitommi or whoever decide on that :)
I've had success running the cljs tests in malli repo in a repl, but I augmented the shadow-cljs.edn
file to load one of the app targets in a browser, and then when the tests were working in the browser I verified them for node by running ./bin/node
this was from cursive though. it should also work with cider with the relevant shadow
integration