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

Question

Is there a way to tell the Chrome debugger (or maybe Firebug?) to not break within certain files? To assume they\'re not broken, essentially? This seems like something they

Answer 1

If the issue you're having is that the Chrome debugger is stopping on all exceptions, even the ones inside of jQuery, then you may need to tell Chrome to only pause on uncaught 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.

Answer 2

1. Go to developer tools setting and click on Balckboxing tab on the left panel.
2. Then click on the Add pattern button and type jquery.js
3. Close and reopen developer tools, now its skipped!

Answer 3

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

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

Update. In Chrome v.75 there is a separabe tab for blackboxing.

Above works in stable Chrome build as well now.

Answer 4

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

In FireFox it's even easier, just click the Eye at the bottom of the file:

Answer 5

The latest version of Chrome has implemented a new blackbox feature that does exactly what you are looking for. Basically, when you set the blackbox option on a given file, it will prevent Chrome debugger from breaking into that file.

This feature is built-in and it can be set with the context menu of the file (right click). It will also work if Chrome debugger is set for stopping on all exceptions.

Answer 6

If the debugger is blowing up somewhere in the jQuery files, you could potentially wrap the suspect calls in a try/catch and then throw an error in your own catch. That way, you can isolate exactly where your're going wrong.

I would be more inclined to do stack traces to see why my code is blowing up, e.g. invalid JSON, than to try gloss over it.