Warning: slightly cheeky post, I have the highest respect for the people behind node-gyp. They’re way smarter than me. If you’ve been working with Node for a while, surely you’ve encountered issues with node-gyp. Searching for the solution can be a frustrating experience. Things get very technical and all kinds of solutions are offered. This is what always works for me. What is node-gyp? I won’t get into the details, because I’m not really bothered with understanding it. I just

We have a NodeJS application that makes HTTP calls to another (.NET) application. Sometimes, when the .NET application returns a HTTP 500 code, our NodeJS application would crash. Needless to say, this is not good. You don’t want one application to crash, because another application encountered an exception. Of course, you don’t want any application to crash, but it’s inevitable. The best thing to do, is to make sure exceptions don’t propagate and take down other applications. The cause, in

I’m currently working on a NodeJS project that makes HTTP calls to an ASP.NET (4.5.1) application. When running locally, I also want to make these calls to my local ASP.NET application. Sometimes, however, I don’t want to start up Visual Studio, open the project, compile, and run. Seeing as this is not ASP.NET Core, I can’t just run it from the command-line. Or can I? It turns out that if you have IIS Express installed (which you should have, with

Mimosa is a build tool for Node.js apps. But it’s more than just building. For a very nice introduction, check out the ‘Tour of Mimosa’ slideshow on their homepage. In short, it will do almost anything you need to get from the source of your web app to something that you can deploy to the server: JS transpiling, CSS linting, JS hinting, minification, dependencies, etc. But it also helps while developing, for example by allowing live reload so you see