Fork me on GitHub
#cider
<
2018-08-31
>
neural02:08:40

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 

neural02:08:37

cider-j-i-cljs works on other project based on lein figwheel... maybe a deps.edn problem ???

dpsutton02:08:28

this error results when "bhauman/figwheel-main" is not on the classpath

dpsutton02:08:17

are you sure that CIDER is issuing the correct command to start it up? does it need an alias?

neural03:08:42

humm... probably that... since i can start figwheel-main from bash... how i override the cider start-up?

dpsutton03:08:55

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

dpsutton03:08:12

that way we can determine if startup is bad and the message is correct or startup is good and the message is erroneous

dpsutton03:08:36

> [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

dpsutton03:08:02

hmm. i wonder why that's using tools.nrepl and not the new 4.0

neural03:08:39

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"])' 

neural03:08:17

@dpsutton and you mean lauch a shell command like that... but configs overrided..

dpsutton03:08:00

if you paste that command into bash can you successfully start your application?

dpsutton03:08:44

i'm not sure i follow what you mean by configs overrided

neural03:08:28

how i can add -A:fib:build to the cider-jack-in-cljs function start?

dpsutton03:08:21

possibly with cider-clojure-cli-global-options. Haven't looked into it

neural03:08:16

@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....

bozhidar06:08:13

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.

bozhidar06:08:50

The real problem is probably the classpath check, something might be wrong with it.

bozhidar06:08:02

Setting cider-check-cljs-repl-requirements to nil will suppress this.

bozhidar06:08:36

(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 )))

bozhidar06:08:59

That’s the relevant code. I wonder why it’s failing for you, as this simply dumps the classpath and checks it.

tianshu07:08:30

how about the eval toplevel form in comment in CIDER, that issue has been closed and the moved into clojure-mode?

bozhidar11:08:05

Yep, this was handled in clojure-mode.

pauld12:08:04

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.

pauld12:08:57

haha looking at caveats now!

pauld12:08:00

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).

pauld12:08:09

browser console that is

bhauman12:08:25

@neural.works.com figwheel.main has to be at the top of your deps.edn not in an alias

reefersleep13:08:25

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.

reefersleep13:08:50

It was a bit of a nasty surprise 🙂

reefersleep13:08:01

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?

reefersleep13:08:44

Guess either is undesireable

dpsutton13:08:07

override it:

(defcustom cider-repl-print-length 100
  "Initial value for *print-length* set during REPL start."
  :type 'integer
  :group 'cider
  :package-version '(cider . "0.17.0"))

neural14:08:04

ok... now i am stuck...

zane19:08:10

Has anyone had success using Cider with figwheel-main without using cider-jack-in?

zane19:08:21

i.e. By launching a nREPL and connecting to it with cider-connect?

rymndhng22:08:36

has anyone encountered this issue where you use cider-find-var, you jump into a jarfile, and then the cider connection is not associated with the buffer of the clojure file? I recall a long time ago this would work fine, is there a setting i've messed up? :thinking_face: