Debugging & Exploring Node.js.pdf

Transcript

1. Debugging & Exploring Node.js Beyond `console.log`
2. Agenda • What's wrong with `console.log`? • The (perhaps not so) golden age of IDEs • The Inspector Protocol • Talk is cheap, let's code
3. So, what's wrong with `console.log`? spoiler: nothing
4. Sometimes there's a better way
6. ever heard about breakpoints and call stack?
8. HOLY JESUS WHERE DID IT COME FROM???
11. Oops, forgot to use `JSON.stringify`
12. We can do better
13. DISCLAIMER
14. THIS TALK IS ABOUT VISUAL AND INTERACTIVE DEBUGGING
15. THIS TALK IS ABOUT VISUAL AND INTERACTIVE DEBUGGING sorry gdb
16. The golden age of IDEs
17. Eclipse
19. Visual Studio (2005)
21. PyCharm
23. Side note Integrated Development Environment
24. Side note Integrated Development Environment
25. Side note Interactive Development Environment
26. Inventing on principle
27. https://hacks.mozilla.org/2012/04/bret-victors-inventing-on-principle-and-a- few-things-it-inspired/ Bret’s big principle is that “creators need an immediate connection to what they create” and shows that right now in most cases this connection is broken. We write code, we compile, we load in a browser and we see the result. That is not immediate but a two steps removed way of creating.
28. Luna Lang
29. https://vimeo.com/250833157
30. The Inspector Protocol
31. The Inspector Protocol • Node.js has a TCP-based built-in debugger that has been deprecated in favor of the Chromium Debugging Protocol, since version 7.7.0
32. The Inspector Protocol • Dead simple, just spawn node.js with the `--inspect` flag and attach a debugger
34. Talk is cheap Let's code