THE DEFINITIVE GUIDE TO DEBUGGING JAVASCRIPT

• FIGURING OUT WHERE THE ERROR COULD BE

• READ THE CODE

• USING THE CONSOLE

• THE CHROME DEV TOOLS

• THE DEBUGGER

• BREAKPOINTS

• SCOPE

• WATCH VARIABLES AND EXPRESSIONS

• RESUME THE EXECUTION

• EDIT SCRIPTS

• INSPECT THE CALL STACK

• BLACKBOX SCRIPTS

  Often times you work with libraries where you don’t want to “step into”, you trust them and you don’t want to see their code in the call stack, for example. Like in the above case for validator.min.js, which I use for email validation.

• USE THE BROWSER DEVTOOLS TO DEBUG NODE.JS

• USE THE BROWSER DEVTOOLS TO DEBUG NODE.JS

  • Open your terminal and run node --inspect
  • Then in Chrome type this URL: about://inspect.

原文：THE DEFINITIVE GUIDE TO DEBUGGING JAVASCRIPT

THE DEFINITIVE GUIDE TO DEBUGGING JAVASCRIPT

原文：https://www.cnblogs.com/rosendolu/p/10241994.html