Editing Website with Chrome DevTools

In this lesson we'll learn

Quick Edits

(⚡️ indicates a tip or trick!)

CSS Specifishity

After watching the quick edits video, please move on to the Exercise

DevTools as an IDE

It helps me to think about the Sources tab as an IDE. Pretend it's VSCode or Sublime Text. On the left is the file tree just as you'd expect, in the middle is the editor itself and this IDE has a bunch of debug tools!




The sources tab is best for debugging more complex problems. It's much easier to edit large amounts of JavaScript, set breakpoints or view an Error stack with this panel.


Limitations (from Chrome DevTools Official Docs)

Chrome DevTools Workspaces allow you to configure an application so that all of the changes you make to the Sources or Elements tab persist to disk. This means you could theoretically use Chrome DevTools as your primary IDE.


If you're using a modern framework, it probably transforms your source code from a format that's easy for you to maintain into a format that's optimized to run as quickly as possible. Workspaces is usually able to map the optimized code back to your original source code with the help of source maps. But there's a lot of variation between frameworks over how they use source maps. Devtools simply can't support all the variations.

Workspaces is known to not work with these frameworks:

If you run into issues while using Workspaces with your framework of choice, or you get it working after some custom configuration, please start a thread in the mailing list or ask a question on Stack Overflow to share your knowledge with the rest of the DevTools community.

After watching the Workspaces video, please move on to the Exercise