This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-08
Channels
- # alda (1)
- # announcements (18)
- # babashka (101)
- # beginners (110)
- # calva (17)
- # cider (53)
- # clara (18)
- # clj-kondo (26)
- # cljdoc (6)
- # clojure (152)
- # clojure-europe (9)
- # clojure-portugal (4)
- # clojure-spec (20)
- # clojure-survey (7)
- # clojure-sweden (10)
- # clojure-uk (10)
- # clojured (1)
- # clojurescript (29)
- # core-async (7)
- # cursive (4)
- # datomic (11)
- # defnpodcast (2)
- # dirac (1)
- # emacs (13)
- # events (2)
- # figwheel-main (1)
- # fulcro (1)
- # jobs (14)
- # jobs-discuss (17)
- # leiningen (2)
- # malli (1)
- # off-topic (74)
- # overtone (1)
- # pedestal (4)
- # planck (2)
- # re-frame (7)
- # reitit (4)
- # remote-jobs (4)
- # shadow-cljs (78)
- # slack-help (3)
- # spacemacs (56)
- # test-check (3)
- # tools-deps (6)
I'm having a terrible time trying to get cider going for a cljs repo. I'm trying to start up a figwheel-main
session but keep getting error in process filter: Figwheel-main is not available.
I've gone so far as to put the library in my main dependencies in the project.clj
but it's not working. Here's the command that is starting up the repl:
[nREPL] Starting server via /nix/store/rdxrnh3w290hdc8gj4zmcbgg5b7q2iri-leiningen-2.9.1/bin/lein update-in :dependencies conj \[nrepl\ \"0.6.0\"\] -- update-in :dependencies conj \[cider/piggieback\ \"0.4.2\"\] -- update-\
in :plugins conj \[cider/cider-nrepl\ \"0.23.0-SNAPSHOT\"\] -- with-profile +cider,+test,+dev,+user repl :headless :host ::
[nREPL] server started on 50397
[nREPL] Establishing direct connection to localhost:50397 ...
[nREPL] Direct connection to localhost:50397 established
error in process filter: user-error: Figwheel-main is not available. Please check for details
error in process filter: Figwheel-main is not available. Please check for details
Anyone have any advice as to how I can figure out what I'm missing?¯\(ツ)/¯
the docs say > This setup is only necessary if cider-inject-dependencies-at-jack-in has been changed from its default setting of enabled, as described more fully above.
so I'm not even clear on why I have to configure anything
also pasted that line into my command line and ran it there and got the same thing I've been getting, so not sure what I can learn from that
if so, to me it demonstrates that your project doesn't work so CIDER couldn't possibly start it up
weird since we've been running it in production for a while
anyways, thanks, will keep poking at it