This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-13
Channels
- # beginners (50)
- # boot (27)
- # bristol-clojurians (7)
- # cider (30)
- # clara (1)
- # cljs-dev (130)
- # cljsrn (14)
- # clojure (179)
- # clojure-austin (6)
- # clojure-greece (2)
- # clojure-italy (4)
- # clojure-spec (19)
- # clojure-uk (54)
- # clojurescript (64)
- # core-async (3)
- # data-science (1)
- # datomic (66)
- # duct (11)
- # emacs (5)
- # figwheel (1)
- # fulcro (26)
- # funcool (7)
- # jobs (1)
- # jvm (6)
- # keechma (5)
- # lein-figwheel (5)
- # luminus (5)
- # lumo (1)
- # off-topic (93)
- # parinfer (37)
- # pedestal (15)
- # protorepl (10)
- # re-frame (42)
- # reagent (12)
- # shadow-cljs (71)
- # spacemacs (3)
- # specter (7)
- # vim (8)
- # yada (9)
Using exp with figwheel, I'm constantly having a problem that minor errors in my code cannot be reloaded successfully, and I need to do variations of restarting everything. What are some known problems in this area? Or am I just have a long run of bad luck?
I suffer from the same problem sadly, I'm not sure what the cause is
I have the expo app crash completely in about every 1 of 2 figwheel reloads
Having worked with exp and cljs for the last ~year, I’m honestly surprised to learn that you have figwheel running with it successfully at all
BRUUUUCE
@chris_johnson What is your workflow?
suffering 😅
We just let the Metro reloaded do its work on file save and don’t attempt to do any sort of hot loading of repl state because it’s too unreliable