Fork me on GitHub
#hoplon
<
2016-11-17
>
fiddlerwoaroof19:11:19

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)

fiddlerwoaroof19:11:03

Or, some kind of embedable REPL I can add to my page tempoarily?

micha19:11:43

@fiddlerwoaroof you should be seeing cljs functions and names in your stack traces

micha19:11:50

is that not what you're seeing?

micha19:11:04

like rather than the generated javascript

micha19:11:10

(source maps)

fiddlerwoaroof19:11:36

I think I'm seeing that

fiddlerwoaroof19:11:15

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

micha19:11:57

yeah i usually ignore all those

fiddlerwoaroof19:11:20

Hmm, I suppose that's what the "blackbox this script" option is for 🙂

micha19:11:43

hm, never heard of that

micha19:11:49

is that a chrome option?

fiddlerwoaroof19:11:12

Yeah, if you open a script in the Sources tab and right click on it, you can blackbox it

fiddlerwoaroof19:11:23

(at least, this option is present in the beta channel)

fiddlerwoaroof19:11:35

I think this means that the debugger will ignore it

fiddlerwoaroof19:11:46

It does: once I blackbox core.cljs and jquery, it shows my files as the source of the error

micha19:11:54

oh interesting

micha19:11:58

that seems useful

micha19:11:44

might be good for the getting started wiki page or something