Skip to main content

​
Your most important tool

Browser DevTools is where you’ll spend a significant chunk of your development time. It lets you inspect the DOM, run JavaScript, monitor network requests, and debug errors — all without leaving the browser.

​
Opening DevTools

Right-click any element on a page and select “Inspect” to jump directly to that element in the Elements panel. This is the fastest way to investigate any part of a page.

​
Elements panel

The Elements panel shows the live DOM tree. You can inspect, edit, and experiment with any element on the page.

​
What you can do

​
Practical uses

  • Debug layout issues: Inspect an element, check its computed size, margin, and padding
  • Test style changes: Edit CSS values live — no need to save and reload
  • Find elements: Use Ctrl+F / Cmd+F in the Elements panel to search by text, selector, or XPath
  • Check accessibility: See element roles, ARIA attributes, and contrast ratios
Changes you make in the Elements panel are temporary — they disappear when you refresh the page. This makes it safe to experiment without fear of breaking anything.

​
Console panel

The Console is where you’ll run JavaScript interactively, see errors, and debug your code.

​
Running JavaScript

​
Console methods

​
Reading error messages

When your code breaks, the console shows the error with a clickable file and line number:
This tells you:
  • What: Tried to read .textContent on something that’s null
  • Where: script.js, line 15, column 23
  • Why: Probably tried to select an element that doesn’t exist (yet)
If you see null errors when selecting elements, your JavaScript is likely running before the DOM is fully loaded. Either move your <script> tag to the bottom of <body>, or use defer: <script defer src="script.js"></script>.

​
Network panel

The Network panel shows every HTTP request the page makes — HTML, CSS, JavaScript, images, and API calls. This is essential for debugging your FastAPI integration.

​
What to look for

  • Status codes: 200 (success), 404 (not found), 500 (server error), CORS errors
  • Request/response bodies: Click a request to see what was sent and received
  • Timing: How long each request takes
  • Headers: Check Content-Type, Authorization, CORS headers

​
Filtering API calls

Click the Fetch/XHR filter to show only API calls (hides images, CSS, etc.). This is the view you’ll use most when debugging your frontend-backend communication.
When debugging API issues, check the Network panel first. It shows exactly what your frontend sent and what the backend returned — no guessing required.

​
Application panel

The Application panel lets you inspect browser storage:
  • localStorage: Key-value pairs persisted between sessions
  • sessionStorage: Key-value pairs cleared when the tab closes
  • Cookies: Data sent with every request to the server
You’ll use this when working with localStorage later in this section.

​
DevTools workflow for debugging

When something isn’t working, follow this order:
1

Check the Console

Look for red error messages. They usually tell you exactly what’s wrong and where.
2

Inspect the element

Right-click the broken element → Inspect. Check if it exists, has the right classes, and has the expected content.
3

Check the Network panel

If data isn’t showing up, check if the API request succeeded. Look at the status code and response body.
4

Add console.log

When the error isn’t obvious, add console.log() statements to trace where values go wrong.

​
What’s next?

You know how to inspect the DOM. Now let’s learn how to find specific elements in it with JavaScript.

Selecting elements

Find and target HTML elements on the page