Chapter 17. Improving app performance with debugging
This chapter covers
- Debugging errors on the client with Chrome Developer Tools
- Debugging errors on the server in Node.js
- Profiling UI performance and memory usage
- Using flame graphs to spot performance bottlenecks
- Debugging Electron apps with Devtron
Humans write programs, and humans make mistakes, even ones that automated testing tools won’t capture. If you’re lucky, you’ll be able to get ahold of a stack trace that reports what error occurred and where it happened in the code.
However, some bugs are subtler and won’t necessarily result in an error. To find these bugs, you need to use tools that can help to diagnose what’s going on in the code, as well as how the app is performing on the computer. Performance is a feature.
In this chapter, I’ll take you through how to use the available debugging tools; I’ll show how to identify and resolve bottlenecks in your front-end code with the developer tools available in both Electron and NW.js, as well as debugging tools for Node.js that can be used to debug errors and analyze performance. I’ll also show you tools for tracking errors that are occurring in your apps as customers use them. Let’s murder some bugs (code ones, not the ones with legs).