You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it is important to note that when console.* is called, browsers* should show the line number and filename in the console mapped to filename and line where the call was made. When a source map is available, the original line number and file names should be displayed instead.
Moreover, I would like to propose introducing a method to enable the correct line number and filename to be displayed when calling console functions through a console abstraction library**.
For example: Angular provides a console.log abstraction called $log. Using $log results in every call displayed as if it originated in angular.min.js on line 79. This solution would enable the log messages to include the line number and filename of where $log.* was called instead.
Node does not currently show this information but it should make it available.
The text was updated successfully, but these errors were encountered:
I think it is important to note that when
console.*
is called, browsers* should show the line number and filename in the console mapped to filename and line where the call was made. When asource map
is available, the original line number and file names should be displayed instead.Moreover, I would like to propose introducing a method to enable the correct line number and filename to be displayed when calling
console
functions through a console abstraction library**.For example: Angular provides a
console.log
abstraction called $log. Using$log
results in every call displayed as if it originated inangular.min.js
on line 79. This solution would enable the log messages to include the line number and filename of where$log.*
was called instead.The text was updated successfully, but these errors were encountered: