Chrome DevTools - Paul Irish wrote a great blog post back in 2016 (updated in 2018) about debugging Node.js using Chrome DevTools, and from the looks of things it sounded pretty simple, and like a great step forward for debugging.įast forward half an hour, and I still hadn’t managed to connect a DevTools window to my simple Node program and I wasn’t so sure anymore.And thinking to myself: there’s got to be a less complex way to do this.
They pretty quickly go down the rabbit hole of UUIDs, WebSockets, and security implications and I start to feel in over my head. It’s useful, but honestly, unless you’ve been programming for a while, it’s not exactly the easiest thing to decipher. Node.js documentation -inspect - The Node.js docs themselves understand debugging isn’t the easiest, so they’ve made a handy reference to help get people started.This is the easiest one to implement, and it’s the fastest way to litter your clean code with extra lines of info - but it can also (sometimes) help you find and fix the error. In Java, it’s (), in Python it’s print() - you get the idea. It’s built in to Node.js and prints in the terminal just like it’s built into JavaScript and prints in the browser’s console. console.log() - the tried and true standby, this one really needs no further explanation if you’ve ever written a line of JavaScript.There’s a number of ways to debug your misbehaving Node.js program, I’ve listed them out below with links to learn more if you so desire.
Let’s go over the debugging options and then I’ll show you the easiest way I’ve come across to debug Node.js in my own development. You just can’t, and it stinks.īut Node is possible to debug, it just takes a little more elbow grease. Unlike JavaScript in the browser, or Java with a powerful IDE like IntelliJ, you can’t just set breakpoints everywhere, refresh the page or restart the compiler and slowly walk through the code examining objects, evaluating functions and finding the mutation or missing variable, etc. If you’ve ever had the pleasure of writing code for a Node.js project, you know what I’m talking about when I say debugging it to figure out what’s going wrong isn’t the easiest thing.
0 kommentar(er)
