Can I tell the Chrome script debugger to ignore jquery.js?

Is there a way to tell the Chrome debugger (or maybe Firebug?) So as not to break in specific files? Suppose they are not broken, essentially? This is similar to what they can create.

+87
javascript google-chrome-devtools
Aug 19 '11 at 20:05
source share
6 answers

Blackboxing JS files is now possible in Firefox https://developer.mozilla.org/en-US/docs/Tools/Debugger

And Chrome Canary uses the Experimental Dev tools. http://www.divshot.com/blog/tips-and-tricks/ignoring-library-code-while-debugging-in-chrome/

Update Chrome v.75 has a separate tab for the black box .

The above works in a stable build of Chrome.

+37
Sep 19 '13 at 8:26
source share

The latest version of Chrome has a new black box feature that does exactly what you are looking for. Essentially, when you set the black box option for a given file, it prevents the Chrome debugger from getting into that file.

This function is built-in, and it can be installed using the file context menu (right-click). This will also work if the Chrome debugger is configured to stop all exceptions.

+28
Jan 28 '15 at
source share

If the problem is that the Chrome debugger stops on all exceptions, even inside jQuery, then you may need to tell Chrome only to pause exceptions, not all exceptions. When in the Script panel in the debugger there is an icon in the lower left corner of the window that controls this.

+15
Aug 19 2018-11-11T00:
source share

In Chrome, open Developer Tools, then go to Settings and you will see the Blackbox tab:

Chrome blackbox

In FireFox, this is even easier, just click Eye at the bottom of the file:

Firefox blackbox

+8
Nov 08 '17 at 22:22
source share
  • Go to developer tool settings and click on the Balckboxing tab in the left pane.
  • Then click the "Add Template" button and enter jquery.js
  • Close and run the developer tools again, now they missed it!
+6
Mar 28 '17 at 8:06
source share

If the debugger explodes somewhere in jQuery files, you can potentially wrap suspicious calls in try / catch and then throw the error into your own catch . This way you can pinpoint where you are going to go wrong.

I would be more likely to do stack traces to understand why my code explodes, for example. invalid JSON than trying to mask it.

+2
Aug 19 '11 at 20:20
source share



All Articles