Debugging JavaScript
Find bugs in JavaScript: console.log to look, reading an error message and its line, and a breakpoint to pause and step through code in DevTools.
Transcript
Bugs happen in JavaScript too. The first tool is console dot log. Print a value, and you can see what it really is.
When something breaks, read the error message. It tells you what went wrong, and on which line. Start there.
A breakpoint pauses your program on a line. In DevTools, open the Sources tab, click a line number, and reload. The program stops, and you can see the value of every variable.
Now step through the code one line at a time, and watch the values change. Predict what the value should be. When it is different, you have found the bug.
Remember: use console dot log to look, read the error message and its line, and use a breakpoint to pause and step. Predict, run, compare, fix.
More in this series
1:2624What is Git?
Git remembers every saved version of a folder. Repository, commit, and the four first commands: git status, add, commit and log.
1:2425The DOM
The DOM is the tree of nodes the browser builds from your HTML. Find a node with document.querySelector and change it with textContent.
1:1926Events in the browser
An event is something that happens on the page. addEventListener waits for it and runs a handler function, shown next to the same idea in Scratch.
1:1827Changing the page
Toggle a class with classList so CSS restyles an element, and build new elements with createElement and append, like a to-do list adding tasks.
1:1528Arrays and objects
An array is a numbered list, an object is a set of labelled values. An array of objects and a loop turn data into cards.
1:2429Local storage and JSON
localStorage is the browser's notebook for your site. JSON.stringify turns an array or object into text to save, and JSON.parse turns it back.
1:2630Fetch and JSON
The browser is the client and fetch sends the request. The server answers with JSON, async and await wait for it, and the Network tab shows what happened.