Debugging TypeScript Applications
Build Web Apps That Don't Break
by: Andrey Ozornin
| Published | 2026-05-12 |
|---|---|
| Internal code | aodjs |
| Print status | In Print |
| Pages | 180 |
| User level | |
| Keywords | |
| Related titles | |
| ISBN | 9798888651988 |
| Other ISBN |
Channel epub: 9798888651995 Channel PDF: 9798888651995 Kindle: 9798888651995 Safari: 9798888651995 Kindle: 9798888651995 |
| BISACs |
Highlight
New code becomes cheaper every day, but maintenance does not. Bugs are faster, subtler, and harder to catch, and dealing with them is increasingly difficult. This book will make it easier, showing you both useful (and underused) features of your browser’s developer console and also ways of writing your code that makes it easier to test (and less likely to need debugging in the first place).
Debug with ease and focus on what truly matters most: building exceptional web applications.
Description
Writing code has never been a problem; getting that code to work is. This book makes it easier, showing you both powerful debugging techniques and also ways to structure to code to make debugging simpler. In just one week you’ll master debugging skills that will save you hours every day.
Read stack traces as if they were a story, wrap risky code in bulletproof guardrails, and triage issues so that critical ones always get fixed first. Master root-cause analysis, design gracefully failing systems, trace data through tangled chains of callbacks and promises, and make resolving future problems easier for everyone with smart error monitoring. Surprise yourself by the power of familiar Chrome developer tools that have always been readily available to you.
Starting from a foundation of process methodologies and software design principles, you’ll continue on through practical techniques like logging and interactive debugging before arriving at monitoring and debuggability. In the end, you’ll have the knowledge you were missing and the skills you need to help you raise the quality bar and focus on what truly matters most: building exceptional web applications.
Happy debugging!
Contents and Extracts
- Change History
- B1.0: December 4, 2025
- Acknowledgements
- Welcome
- Is This Book for Me?
- What’s in This Book?
- How to Read This Book
- Before We Begin
- Printing and Interpreting Errors
- Setting Up for the Book
- Getting Started with Debugging
- Fixing Common Errors
- Wrapping Up
- Setting Guardrails with Throw and Catch
- Fail-Fast and Fault-Tolerant Systems
- Advanced Logging
- Wrapping Up
- Prioritizing Bugs
- Estimating Bug Severity
- Estimating Bug Reach
- Estimating Bug Fix Time
- Prioritizing Bugs Using RICE
- Prioritizing Beyond Methodologies
- Wrapping Up
- Finding the Root Cause
- Finding the Reproduction Steps
- Using Systems of Root-Cause Analysis
- Using the Scientific Method
- Finding the suspect commit using git bisect
- Wrapping Up
- Designing Software That Doesn’t Break
- Write Clean Code
- Let Your Computer Help You
- Assure Quality with Automated Testing
- Ship with Confidence
- Wrapping Up
- Following the Data Flow
- Defining What “Fixed” Means
- Overcoming Blank Console Paralysis
- Getting to Know the Sources Panel
- Navigating the Code
- Using Breakpoints
- Improving the Fix
- Using Source Maps
- Wrapping Up
- Bonus Exercise
- Debugging Asynchronous Operations
- Network Panel in Chrome Developer Tools
- Debug Parallel Operations
- Logging on a Webpage
- Wrapping Up
- Make Your Code Debuggable
- Setting Up Sentry
- Monitoring Errors
- Structured Logs
- Adding Performance Traces
- Wrapping Up