I spent a few days, recently, tracking down a memory leak in a production NodeJS system. I found the leak. But the journey to get there was not exactly scientific, repeatable, or one that I would wish on anyone else. If tracking down memory leaks sounds difficult to start with, the reality of doing it […]
A question was asked via twitter: @derickbailey @rauschma What do you think about adding methods on built-in prototypes (e.g. String.prototype)? — Boris Kozorovitzky (@zbzzn) June 30, 2015 So, I built a simple flow chart to answer the question (created w/ draw.io) All joking aside, there’s only 1 situation where you should patch a built in object […]
Over the weekend, I attended and spoke at the Nodevember conference in Nashville, TN. At this conference, I spoke on the subject of destroying your IDE in favor of using smaller, light-weight, flexible and composable tooling like Grunt, Grunt-Contrib-Watch and others. I had a strongly positive amount of feedback from the session, which is always […]
I found myself needing to run a debugger on my Jasmine specs. The really fun part is that I am running these specs through the grunt-jasmine-node plugin for grunt. This means what I really need to do is run a debugger on top of grunt, and have it hit my Jasmine specs when they get around to being executed.
In a previous post, I showed how to run browserified unit tests in a headless browser using PhantomJS and grunt-contrib-jasmine. Shortly after posting that, I found myself needing to run a debugger on my tests (because console.log debugging is not sufficient). What to do? How do I get a debugger attached to my grunt-contrib-jasmine specs? […]