Node v4.0.0 - Hackdot

Re:Node v4.0.0 by blowski on Tuesday September 08, 2015 @05:47PM (#10188389)

Sure. There was the decision a couple of years back to stop using self signed certificates. I spent a couple of hours wondering why a server I was running that compiled SASS on deployment suddenly stopped working, and it turned out to have been this.

A more recent example comes from Zombie, which I use for functional testing. When they moved to v3, they required io.js instead of Node. So eventually I decided to go with Zombie 3 and moved to io.js, but then another library broke which required Node instead of io.js.

They're the two big ones that stand out, but there have been lots of other small annoyances.

[ Parent | on HN ]

Re:Node v4.0.0 by brazzledazzle on Tuesday September 08, 2015 @06:16PM (#10188506)

I don't have a dog in this fight but the certificate thing sounds a lot like they corrected a significant security issue rather than API instability.

[ Parent | on HN ]

Re:Node v4.0.0 by blowski on Tuesday September 08, 2015 @06:22PM (#10188533)

True enough, but they didn't tell anyone they'd done it for hours after they pushed out the changes. A notice on the terminal after the update should have been possible, or at least a big message on the homepage. But nothing - only an angry GitHub issues queue with random suggested causes and fixes.

[ Parent | on HN ]