resolving the proper location and line number through a console.log wrapper

readme.md

console.log wrap resolving for your wrapped console logs

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

Blackbox the source file:

You can right-click the file in the editor, as well. Or blackbox via regex in Settings.

Logs will be resolved back to their call frame.

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

@wixo also supports line numbers: https://github.com/patik/console.log-wrapper/ and logs in legacy browsers (but no line numbers there)

👍

That's great! Thanks so much! Is it also possible to filter out 3rd party libraries from the stack trace by blackboxing? :D

Semantic UI uses a slightly different implementation for wrapping console calls that preserves line numbers and doesn't require blackboxing.

module.debug = function() {
  if(settings.debug) {
    // overwrite self
    module.debug = Function.prototype.bind.call(console.info, console, settings.name + ':');
    module.debug.apply(console, arguments);
  }
};

We also use a console.table to do grouped performance logging, console.groupCollapsed is epic.

thanks

Any tips for Firefox users?

here's the FF bug about implementing this https://bugzilla.mozilla.org/show_bug.cgi?id=1060904

and here is the Edge bug https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/18045530/