I've heard this before:
What I really get frustrated by is that I cannot wrap
console.*
and preserve line numbers
We enabled this in Chrome DevTools via blackboxing a bit ago.
If you blackbox the script file the contains the console log wrapper, the script location shown in the console will be corrected to the original source file and line number. Click, and the full source is looking longingly into your eyes.
You can try it out here: http://plnkr.co/edit/3wg4u9HUGXfFH0U7MR7j
You can right-click the file in the editor, as well. Or blackbox via regex in Settings.
FWIW, Blackboxing does a lot. Blackboxing a file means:
- Exceptions thrown from library code will not pause (if Pause on exceptions is enabled),
- Stepping into/out/over bypasses the library code,
- Event listener breakpoints don't break in library code,
- The debugger will not pause on any breakpoints set in library code.
Read more about it over at https://developer.chrome.com/devtools/docs/blackboxing
Cheers and thanks crbug/249575
Very nice and I was hoping to see some way to automatically whitelist the blackboxed URLs - the regex list didn't disappoint.
Suggestion for further improving it: Standardise the whitelist into a manifest.json equivalent (dev.json or something) so the default setting can be part of the project instead of (or in addition to) the browser settings. It would be a hassle for every developer of a project to have to configure the same whitelist manually after checkout and whenever it needs to change.