When an SSL connection fails in node.js, node.js usually gives you a helpful error message like “ECONNRESET” or “unable to verify the first certificate”. These errors don’t always tell you what is going wrong. Worse, if you go looking on stack overflow, you’ll usually get helpful advice like setting
rejectUnauthorized: falseor set the
NODE_TLS_REJECT_UNAUTHORIZEDenvironment variable to 0; these are terrible suggestions because the take away almost all of the security that you’re hoping to gain by using SSL in the first place.
Here is a list of interesting reasons why node.js fails to connect to an SSL server, and how to fix them. If you have any situations you’ve run into that are missing here, feel free to chime-in in the comments below.
I recently set up a Hue lightbulb in our office to show red when our Travis-CI builds are failing, and green when they pass. This was done with a mix of AWS Lambda and IFTTT.
At my office, we’re a coffee-script shop. Of late, though, more and more of the cool features of coffee-script seem to be getting ported to Ecmascript 2015, and with node.js now supporting many of these features, I decided it was time to try out a small project in ES2015. The TL;DR here is that Babel is a nice way to access fancy ES2015 features, even ones that aren’t in the latest node.js, but Babel comes with a significant compile-time overhead.
With Atom 1.0 out, a revised list of handy plugins I’ve found for the Atom text editor.
subscribe via RSS