Debugging frontend js with chrome dev tools
Qwertyzw last edited by Qwertyzw
What is the ideal way to approach debugging scripts that run on page load?
For some reason I get the same behavior with nodebb.min.js. The breakpoints are all lost on refresh, although the resource name is the same every time (
The only way I can think of is to cause whatever is meant to run on a page load to run on some sort of a specific event that is triggered after I got a chance to set the breakpoints. Or simply flood the code with
@Qwertyzw you could put a
debugger;statement where you want it to break.