This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-17
Channels
- # aws (10)
- # beginners (64)
- # boot (3)
- # cider (20)
- # cljs-dev (32)
- # cljsrn (6)
- # clojure (126)
- # clojure-dusseldorf (3)
- # clojure-finland (1)
- # clojure-greece (1)
- # clojure-italy (7)
- # clojure-poland (3)
- # clojure-spec (46)
- # clojure-uk (100)
- # clojurescript (37)
- # cursive (11)
- # datomic (6)
- # defnpodcast (2)
- # emacs (1)
- # events (3)
- # figwheel (2)
- # fulcro (20)
- # immutant (2)
- # jobs (1)
- # jobs-discuss (9)
- # keechma (3)
- # lein-figwheel (1)
- # luminus (2)
- # lumo (3)
- # mount (2)
- # off-topic (19)
- # om (3)
- # om-next (2)
- # onyx (20)
- # other-languages (55)
- # parinfer (11)
- # pedestal (8)
- # portkey (3)
- # protorepl (3)
- # re-frame (22)
- # ring (9)
- # rum (1)
- # shadow-cljs (82)
- # spacemacs (28)
- # sql (15)
- # test-check (15)
- # testing (2)
- # tools-deps (102)
- # vim (26)
Btw, @dominic did some outstanding job extending the test filter support in cider-nrepl
and I’ve just updated the code in CIDER to make use of the improve middleware capabilities. Now you can select multiple include/exclude filter selectors when running tests via CIDER.
It's likely if cider-shadow-cljs-command
is npx shadow-cljs
(default value), in cider-jack-in
it will use npx
, not npx shadow-cljs
. and this will cause an error.
@doglooksgood I don’t quite follow. Why would this happen?
Ah, now I see what you mean. We’re using just resolved command without its second part.
I have this problem with latest cider, in the REPL, I can do:
> (require '[clojure.spec.alpha :as s])
nil
never mind
I’m running into an issue where the REPL dies after C-c C-c
and reverts to being a REPL. Anyone else encounter this?
the status is in the "done" response to an op. what op are you doing that it returns with the new erroneous repl type?
back in the day it would use the cljs connection but would remember the clj session id so that it would get clj stuff back and the middleware would report that this connection was a clj connection
@xiongtx Monitor the message coming from track state. Might be mistaken case of identity there. Lately I’ve been wondering if we should track the REPL type via the middleware at all.