This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # babashka (14)
- # beginners (62)
- # calva (1)
- # cider (54)
- # clj-kondo (3)
- # cljdoc (15)
- # cljs-dev (2)
- # clojure (180)
- # clojure-europe (5)
- # clojure-italy (4)
- # clojure-losangeles (1)
- # clojure-nl (2)
- # clojure-spec (10)
- # clojure-uk (39)
- # clojurescript (85)
- # core-async (9)
- # core-logic (1)
- # core-typed (5)
- # crux (2)
- # data-science (27)
- # datomic (2)
- # emacs (15)
- # figwheel-main (98)
- # fulcro (26)
- # graphql (15)
- # helix (1)
- # jobs-discuss (26)
- # kaocha (1)
- # off-topic (54)
- # other-lisps (1)
- # re-frame (21)
- # reagent (1)
- # reitit (3)
- # shadow-cljs (49)
- # spacemacs (12)
- # specter (5)
Does anyone has issue with autocompletion with the newest cider, clojurescript and shadow-cljs? I get a null pointer exception.
I can't get the refactoring tools or company mode to work, but I haven't looked into it much.
You can create new .clj files the normal Emacs way with
find-file , and if you have clj-refactor it will automatically add the ns form
Hey. Shadow-cljs, latest cider - when I cider-connect to an nrepl port, all seems well and I get a repl in Emacs, however, all commands from a src buffer give me:
user-error: No cljs REPLs in current session...
@phil638 Are you using shadow-cljs 2.10? There were some big changes to its internals, so it might be something related to that. There hasn’t been any recent changes on CIDER’s end with respect to shadow and cljs in general.
The error you got seems to indicate something went wrong in the REPL init process, which might be related to something wrong in shadow. Not sure.
@bozhidar I'm finding
cider--match-repl-type is seeing
pending-cljs when it's looking for
the buffer should be set to cljs when it connects to a running app, either node or the browser. has this happened yet?
it never got set then i guess. there's a bit of a complicated state tracker in there
But it’s not complicated actually - all it checks for is the presence of a piggieback session, nothing more.
i would probably toggle nrepl message logging and then restart the repl. then watch the messages in startup and watch for the repl-type keyword
nrepl-toggle-message-logging and see if this message comes:
(<-- id "10" session "f042944b-6101-46a7-a80f-653115475bfb" time-stamp "2020-06-05 11:23:59.380273000" changed-namespaces (dict ...) repl-type "cljs" status ("state") )
Almost every time someone experienced this problem it turned out that this cljs check wasn’t working.
time-stamp "2020-06-05 17:31:05.659201954"
status ("done" "unknown-op" "error")
sounds like a bad nrepl server then. i think everyone should be able to respond to version?
Ok, what's the helpful thing for me to do, raise a bug with all of this information?
but this should probably be a ticket/issue. CIDER should handle the lack of cider-nrepl gracefully if missing features
Good point. It seems it used to handle it just fine before the pending state was added, as I see in the state handler that it does nothing in the absence of the middleware. I assume before we added pending the state started as cljs and probably we need to do something similar.