This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-06
Channels
- # beginners (137)
- # cider (60)
- # cljs-dev (52)
- # cljsrn (5)
- # clojars (15)
- # clojure (156)
- # clojure-brasil (1)
- # clojure-dev (7)
- # clojure-italy (13)
- # clojure-serbia (2)
- # clojure-spec (12)
- # clojure-uk (76)
- # clojurescript (129)
- # core-async (27)
- # core-typed (1)
- # cursive (3)
- # datomic (105)
- # devcards (39)
- # emacs (10)
- # figwheel (1)
- # fulcro (68)
- # graphql (6)
- # juxt (3)
- # klipse (85)
- # lein-figwheel (47)
- # leiningen (3)
- # midje (1)
- # mount (26)
- # off-topic (71)
- # om (4)
- # overtone (4)
- # parinfer (3)
- # pedestal (4)
- # portkey (37)
- # re-frame (37)
- # reagent (13)
- # reitit (3)
- # ring (1)
- # rum (5)
- # shadow-cljs (191)
- # spacemacs (35)
- # specter (26)
- # tools-deps (45)
- # vim (20)
I am not sure they support that yeah...never heard of it
hi, with latest CIDER from MELPA I get this every time I try to do cider-load-buffer
:
Caused by clojure.lang.ExceptionInfo
No such namespace: cheshire.core, could not locate cheshire/core.cljs,
cheshire/core.cljc, or JavaScript source providing "cheshire.core"
cheshire
is in my project.clj
and I can run my project (and the tests) without any issues. Do you want me to report it on GitHub?@manuel seems like Cheshire is a clj only lib and you're trying to use it from Clojurescript?
Odd. But it's trying to load it in a cljs environment from what I can see. It's looking for a cljs/cljc source file
well, I did cider-jack-in-clojurescript
because it is clj/cljs project, but still I did cider-load-buffer
from a clj file
@manuel Maybe something’s wrong with the connection mapping? Can’t tell you more without being able to play with some reproducible example.
I don’t think anything important has changed recently, though - except auto-injection of cljs deps. You can try disabling it to see if that won’t fix your problem, although I can’t imagine how it could cause what you’re describing.
i think there's still some incompatability with figwheel piggieback and cemerick. i'm still trying to track it down
Yesterday Bruce fixed a problem FYI in Piggieback: it was not threading in some compiler options
@bozhidar the figwheel repl launches a node process, and it would be nice if there was a finally block in nrepl that sends a tear-down message through the middleware stack, because if folks don't :cljs/quit from the cljs repl it seems to hang. This may be an none issue, as it may just be Reply's handling of shutdown, still investigating. But ... the nature of the system doesn't really allow for clean up.
yeah its only a problem when I do control-D out of reply
it leaves a node process running on my machine
@bhauman is the new piggieback
in a SNAPSHOT
? Cannot use gitlibs because of https://github.com/clojure-emacs/cider/issues/2308
(I mean I can clone it of course 😉 just asking)
lein deploy clojars
(maybe)
ok I am trying thanks!
@richiardiandrea but I haven't release the figwheel.main yet
cloning both
awesome
figwheel-main
can now become a proper repl type 😄
I'd really like this to be more configurable, need to be able to supply args to figwheel.main start
cider
usually has configurable command line strings so probably we can take the same approach
the problem is how to make the REPL forms configurable enough
say you want to launch different builds .... this is a more general cider improvement though
at some point I wanted to have something like a "plugin" in inf-clojure
where you declare your maven deps and a function that will be called for configuration (that sends forms to the repl)...didn't have time to expand it and dropped it 😄
this is probably an unnecessary complication, as we could just add functions specific to figwheel, for instance, that produce the form to send...with defcustom
s ad-hoc for its options
and that's how a cider-figwheel.el
was born 😄
@bhauman @bozhidar quickly hacked https://github.com/clojure-emacs/cider/pull/2313
yes I just opened it for discussing more about it 😄