liveBook · Manning

Debugging

As explained in Secrets of the JavaScript Ninja, Second Edition

The process of finding, inspecting, and correcting software defects or unexpected behavior.

When a web application behaves unexpectedly, debugging means investigating its JavaScript and browser behavior. Browser developer tools offer a richer alternative to checking values with alerts. section 1.3.1 section 1.3

Choose the developer tools available in the browser where you are investigating the problem:

  • Firebug for Firefox; Chrome DevTools for Chrome and Opera; Firefox Developer Tools; F12 Developer Tools for Internet Explorer and Microsoft Edge; or WebKit Inspector for Safari. section 1.3.1
  • These tools share capabilities for exploring the DOM, debugging JavaScript, editing CSS, and tracking network events. Some, including Chrome DevTools, can also debug Node.js applications. section 1.3.1

How Secrets of the JavaScript Ninja, Second Edition covers it

How deep it goes
Compares browser-tool capabilities but leaves specific debugging techniques for later.
Examples
Contrasts JavaScript alerts with Firebug, Chrome DevTools, Firefox Developer Tools, F12 Developer Tools, and WebKit Inspector.
What it assumes
Assumes familiarity with JavaScript and web applications; contrasts developer tools with alert-based checks.
What you can do after
Operate browser developer tools to inspect JavaScript, the DOM, CSS, and network events.
How it connects
Connects debugging with the DOM, CSS, network events, Node.js, testing, and performance analysis.

Also explained in

Compare how 16 books explain debugging →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Secrets of the JavaScript Ninja, Second Edition. The section links point to the parts of the book it draws on.