This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-17
Channels
- # aws (3)
- # beginners (81)
- # boot (155)
- # capetown (2)
- # cider (32)
- # clara (14)
- # cljs-dev (40)
- # cljsrn (12)
- # clojure (158)
- # clojure-austin (5)
- # clojure-korea (6)
- # clojure-poland (1)
- # clojure-russia (63)
- # clojure-spec (45)
- # clojure-uk (75)
- # clojurescript (109)
- # code-reviews (1)
- # core-logic (12)
- # core-matrix (1)
- # cursive (36)
- # datomic (16)
- # defnpodcast (1)
- # devcards (2)
- # editors (3)
- # euroclojure (1)
- # events (3)
- # flambo (1)
- # hoplon (19)
- # javascript (4)
- # jobs (1)
- # lein-figwheel (4)
- # leiningen (1)
- # off-topic (1)
- # om (177)
- # onyx (121)
- # pedestal (14)
- # planck (19)
- # proton (3)
- # re-frame (36)
- # reagent (21)
- # remote-jobs (1)
- # ring (4)
- # ring-swagger (6)
- # spacemacs (1)
- # specter (2)
- # test-check (4)
- # untangled (9)
- # utah-clojurians (1)
- # yada (2)
Is there a way to make Chrome's developer tools more helpful? (i.e. stack traces that highlight my code rather than showing a bunch of stuff about the inner workings of hoplon)
Or, some kind of embedable REPL I can add to my page tempoarily?
@fiddlerwoaroof you should be seeing cljs functions and names in your stack traces
I think I'm seeing that
The problem is that it's really difficult to find what part of my code is causing the problem because most of the lines in the stack trace are from core.cljs
Hmm, I suppose that's what the "blackbox this script" option is for 🙂
Yeah, if you open a script in the Sources tab and right click on it, you can blackbox it
(at least, this option is present in the beta channel)
I think this means that the debugger will ignore it
It does: once I blackbox core.cljs and jquery, it shows my files as the source of the error