Old protocols and new protocols, Visual Studio Code and Chrome DevTools, async traces and dynamic stepping... So many new capabilities and tools have been released this year to make debugging and diagnosing Node.js apps easier, and so many more are in development in core and in vendor products. But how to start using them and what to do when things go wrong? What caveats and tips should everyone be aware of? In this session we'll "debug debugging" - turn the system inside out so you can understand how it's supposed to work from core's perspective. You'll leave better prepared to utilize the rush of new tools and better armed to address unexpected problems. You might even discover ways you can contribute to the Diagnostics WG and help us continue to improve the quality of Node.js apps!
