Fork me on GitHub
#cljsrn
<
2018-02-13
>
deg14:02:53

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?

danielneal14:02:49

I suffer from the same problem sadly, I'm not sure what the cause is

danielneal14:02:12

I have the expo app crash completely in about every 1 of 2 figwheel reloads

chris_johnson15:02:43

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

deg16:02:32

Ouch. I guess I'm glad to hear that it's not just me. ???

deg16:02:16

@chris_johnson What is your workflow?

chris_johnson16:02:42

suffering 😅

chris_johnson16:02:51

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

deg16:02:39

Ok thanks. (anyone else reading this have any better luck?)

jeaye22:02:33

I use figwheel daily, without too much issue, but I'm not using expo.

jeaye22:02:31

Daily repentance is needed with any cljsrn work, bear in mind.

jeaye22:02:49

From what I've seen, expo tends to make things more complicated, rather than less.