This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-16
Channels
- # announcements (9)
- # babashka (12)
- # beginners (60)
- # biff (2)
- # calva (4)
- # cider (4)
- # clj-commons (1)
- # clj-kondo (17)
- # clojure (2)
- # clojure-europe (17)
- # clojurescript (15)
- # emacs (18)
- # exercism (5)
- # fulcro (15)
- # holy-lambda (13)
- # joyride (1)
- # lambdaisland (2)
- # malli (1)
- # nbb (3)
- # off-topic (23)
- # polylith (6)
- # portal (59)
- # releases (1)
- # squint (1)
- # tools-deps (4)
hey guys, any idea what could be wrong when I'm getting thi when I cider-jack-in-cljs
in a simple shadow-cljs project? happens with this <https://github.com/shadow-cljs/quickstart-browser>
Did you remember to start the watch process with npx shadow-cljs watch app?
but that's the thing, I've already asked in other places and it seems cider-jack-in-cljs
should detect shadow-cljs and start the watch when you jack in automatically, no?
even if I do start it manually with npx shadow-cljs watch app
and then cider-connect-cljs
and it does connect it doesn't seem to work, as eval-ing expressions "doesn't do anything", for example if I eval (js/alert "foo")
it won't open an alert, even though emacs acts like if it did eval ... I do get recompile/reload on save, but that's coming from npx shadow-cljs watch app
that runs independently from CIDER/emacs, seems nothing on the emacs side works
but in a similar project that uses figwheel I can eval things with CIDER the same way, and "it works", as in eval-ing things actually evaluates them as expected
if I open a similar example project with