Supercharge your debugging experience for Node.js
You see this, what do you do?
hypothetical: You might check every line of code and try to find a typo. No typo found… next you might start using console.logs to see the output for code, which is a pain. Surely there are better methods out there?
Console logs just simply aren’t enough since it requires us to go line by line in a very slow manner whilst restarting our server each time. Console logs also clutter our codebase with unnecessary code and removing them requires small effort.
Exhibit A: How much energy does it take to spot the console log among the dummy data and other processes?
Very taunting. It doesn’t have to be this way.
Much more efficient way of doing things would be debugging with breakpoints. With breakpoints we can step over the call stack and event loop to diagnose the problem.
You get the point. Time to explore other options. What are the options? I’m glad you asked!
By the way there’s a very tasty treat at the end of the article — just sayin.
Node has a built-in inspector!
Let me show you — let’s start a new node project.
Now we have a basic express server. But instead of using the
node server.js command the traditional way, we’re adding a extra flag to our node command, the inspector.
--inspect tells Node to expose the new debugging protocol.
Once we start our server with the inspector, here’s what the console outputs.
Sweet, it worked. Open the Chrome at http://localhost:3000 with the dev tools. Notice something extra?
Woot, node inside our browser? Yes indeed! We still consume our app like before —
http://0.0.0.0:9229/ port is for the DevTools to consume.
What does Node Inspector do?
Node Inspector lets you to use the DevTools user interface with the native Node debugger. DevTools can now connect directly to the Node process!
If you know how to get this working on Firefox or Safari, let us know in the comments/discussion.
Using the debugger
Using the chrome debugger is very much the same like using the debugger for client side code. You set breakpoints, execute the code, step over the breakpoints and find the bug.
Can you imagine how useful this can be when we have an error inside a big controller? We have access to the debugger, call stack, scopes, local variables, global variables, etc. We have so many sharp tools to use!
Taking it to another level
We’re not done yet. Yesterday (20 July, 2018) was a very special day for debugging node. Why?
Google Chrome labs team open sourced their advanced debugging tool — ndb!
Ndb is a sweet tool for debugging. Let’s give it a go.
npm install -g ndb
It’s like any other npm package, very simple to use and install.
To use ndb, we just have to prefix our start script with ndb.
That’s all! Let’s restart our server — notice we’re using nodemon — just like any traditional project.
Woot! We have a new chrome instance for the sole purpose of debugging. How cool is that? Epic!
We even have access to the node
process global object — which is the
window object for node.
Hacker news discussion about the new debugger — check it out!
That said, with both VSCode and WebStorm, I've seen finicky issues from time to time, like source maps not working…news.ycombinator.com
Thanks for reading, stay awesome! ❤
The latest Tweets from Indrek Lasn (@lasnindrek). Author, software engineer, founder. Spread the love ❤. Zurich…twitter.com
Separating your frontend and backend has many advantages:medium.freecodecamp.org
Due to high demand I’m extending the list of fun apps to build. 😁medium.freecodecamp.org
Let’s talk about events, more specifically pointer events.codeburst.io
What is a rich text editor anyway?medium.com