This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-31
Channels
- # announcements (3)
- # beginners (139)
- # boot (28)
- # cider (40)
- # cljdoc (1)
- # cljs-dev (30)
- # clojure (61)
- # clojure-conj (1)
- # clojure-dev (113)
- # clojure-germany (4)
- # clojure-italy (29)
- # clojure-nl (3)
- # clojure-russia (2)
- # clojure-spec (38)
- # clojure-uk (53)
- # clojurescript (188)
- # core-async (4)
- # css (2)
- # cursive (7)
- # data-science (5)
- # datomic (14)
- # emacs (1)
- # figwheel-main (192)
- # fulcro (37)
- # jobs-discuss (1)
- # mount (4)
- # off-topic (47)
- # pedestal (7)
- # portkey (14)
- # re-frame (4)
- # reagent (22)
- # reitit (2)
- # remote-jobs (1)
- # ring (6)
- # shadow-cljs (65)
- # spacemacs (7)
- # specter (6)
- # yada (8)
in cider-jack-in-cljs getting this after choose repl figwheel-main
error in process filter: user-error: Figwheel-main is not available. Please check
error in process filter: Figwheel-main is not available. Please check
cider-j-i-cljs works on other project based on lein figwheel
... maybe a deps.edn problem ???
are you sure that CIDER is issuing the correct command to start it up? does it need an alias?
humm... probably that... since i can start figwheel-main from bash... how i override the cider start-up?
start it up like normal and check in the *Messages*
buffer to see what command it invoked. make sure it looks similar to what you need to start up
that way we can determine if startup is bad and the message is correct or startup is good and the message is erroneous
> [nREPL] Starting server via /usr/local/bin/clojure -Sdeps '{:deps {org.clojure/tools.nrepl {:mvn/version "0.2.13"} cider/cider-nrepl {:mvn/version "0.18.0"}}}' -e '(require (quote cider-nrepl.main)) (cider-nrepl.main/init ["cider.nrepl/cider-middleware"])'... something like that
same here
[nREPL] Starting server via /usr/local/bin/clojure -Sdeps '{:deps {org.clojure/tools.nrepl {:mvn/version "0.2.13"} cider/piggieback {:mvn/version "0.3.8"} cider/cider-nrepl {:mvn/version "0.18.0"}}}' -e '(require (quote cider-nrepl.main)) (cider-nrepl.main/init ["cider.nrepl/cider-middleware", "cider.piggieback/wrap-cljs-repl"])'
@dpsutton cider-clojure-cli-global-options
let you add some options.. trying to override the -Sdeps in function call... i think that tools.nrepl is wrong....
The injection of tools.nrepl is only for the benefit of lein repl
users on an older tools.nrepl. I’ll likely remove it, as it seems to confuse a lot of people.
(defun cider-check-figwheel-main-requirements ()
"Check whether we can start a Figwheel ClojureScript REPL."
(cider-verify-piggieback-is-present)
(unless (cider-library-present-p "bhauman/figwheel-main")
(user-error "Figwheel-main is not available. Please check )))
That’s the relevant code. I wonder why it’s failing for you, as this simply dumps the classpath and checks it.
how about the eval toplevel form in comment in CIDER, that issue has been closed and the moved into clojure-mode?
Hi, I was wondering if there a section in http://docs.cider.mx that describes what is likely to work or not work when using clojurescript? For instance, cider-inspect-last-result gives an error, but I figure it's probably just one of the many features of cider that doesn't work for a clojurescript repl.
I wonder if most cider users just print their data to the console. With devtools in chrome it's not bad. I've been using (js/console.dir data).
@neural.works.com figwheel.main has to be at the top of your deps.edn not in an alias
How come *print-length*
is 100 in CIDER instead of nil? My colleagues and I are experiencing an error where we thought we were storing a data structure as a string, but the structure is cut off if it exceeds the print-length size. That is, our data structure is {:stuff [x y …]}
instead of {:stuff [x y z foo bar]}
for a sufficiently big structure.
It was a bit of a nasty surprise 🙂
I mean, I get the intention, I think. Avoid flooding the REPL. Maybe I’m just unsure of whether it’s the better default. Let the user figure out how to avoid flooding the REPL if they want to rather than corrupt their data?
Guess either is undesireable