This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-26
Channels
- # announcements (2)
- # aws (4)
- # babashka (5)
- # beginners (91)
- # calva (4)
- # cider (17)
- # clara (13)
- # clj-kondo (14)
- # cljsrn (11)
- # clojure (159)
- # clojure-europe (2)
- # clojure-nl (14)
- # clojure-norway (2)
- # clojure-taiwan (2)
- # clojure-uk (32)
- # clojurescript (101)
- # clojutre (4)
- # cursive (13)
- # data-science (1)
- # datomic (46)
- # emacs (68)
- # figwheel-main (5)
- # fulcro (48)
- # graalvm (7)
- # graphql (6)
- # instaparse (5)
- # joker (4)
- # lambdaisland (1)
- # leiningen (2)
- # malli (9)
- # off-topic (41)
- # pedestal (15)
- # re-frame (47)
- # reagent (7)
- # reitit (14)
- # shadow-cljs (180)
- # spacemacs (58)
- # specter (1)
- # tools-deps (13)
I’m just starting out with figwheel So far I’m really impressed. The only problem is that I can’t figure out how to create a reliable repl setup so that I can evaluate code directly from Cursive. I’ve followed the tutorial: https://figwheel.org/docs/cursive.html. The setup works in principle but frequently when I evaluate ClojureScript code that throws errors the console inside of Cursive looses the connection to the browser and I can no longer evaluate anything. Restarting the repl inside of Cursive is the only thing that helps. Do you have any pointers what I’m doing wrong?
I’ve realized the problem also occurs when running the repl from a regular terminal. The problem seems to be the following issue: https://github.com/bhauman/figwheel-main/issues/161