This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-27
Channels
- # announcements (5)
- # beginners (267)
- # boot (1)
- # calva (37)
- # cider (11)
- # clara (10)
- # clj-kondo (24)
- # cljsrn (13)
- # clojars (1)
- # clojure (119)
- # clojure-europe (5)
- # clojure-italy (19)
- # clojure-nl (11)
- # clojure-spec (18)
- # clojure-uk (99)
- # clojurescript (44)
- # clojurex (57)
- # community-development (6)
- # cursive (13)
- # datomic (92)
- # duct (12)
- # fulcro (1)
- # graalvm (4)
- # jobs (1)
- # kaocha (6)
- # luminus (3)
- # lumo (9)
- # off-topic (20)
- # pathom (6)
- # re-frame (21)
- # reagent (2)
- # reitit (9)
- # remote-jobs (4)
- # shadow-cljs (32)
- # spacemacs (3)
Is there any way to make React Native stack traces more usable with ClojureScript? Debugging any exception is extremely painful - there seems to be absolutely no way to precisely locate the error. I have cljs-devtools installed.
The trick is to enable remote debugging in chrome, and then put "pause on caught exceptions on"
if you've got sourcemaps, that should take you to the exact line
(sometimes)
good luck!
@xfyre any luck?
you can pre-emptively test it with a throw...
sometimes you need to skip through caught exceptions in the innards of the framework, too
did we do this for this channel? https://clojurians.slack.com/archives/C0CB40N8K/p1561654737007100