Running tests in a container didn’t add too much to our configuration with Grunt or Docker. But there are a few tricks that you’ll want to know, when debugging.
Learn how to configure Visual Studio Code (or any other remote capable debugger) to debug Node.js in a Docker container.
Learn how to start an application instance in a Docker container, with the Node.js debugger already attached so you can debug issues that occur when the application starts.
Learn how to attach a debugger to code that is already running inside of a container, maintaining the current application state and allowing you to find and fix bugs quickly.
Some recent discussion in the WatchMeCode slack spawned a bit of research into creating custom errors through factory methods, while keeping the stack trace for those errors clean, in Node.js After a bit of digging, I found a good solution using Node’s Error.captureStackTrace method, and recorded a quick screencast to highlight it’s use.
In the previous episode, the Keen.io code for the analytics service was moved into a separate process using RabbitMQ. Toward the end of the episode, however, there were a number of issues that we ran into – most notably was an error in syntax not being reported correctly. In this episode, you’ll see the root […]