Hacker News Reader

Comment by pornel | Hacker News Reader

I'd like to use this as an opportunity to remind everyone that Node.js v4 is going to be dead in about a month (support for it has ended long time ago, and now it's the end of extended support).

If you haven't upgraded Node in the last two years, this is the last call.

View on HN

Slightly problematically - a lot of AWS's default Node infrastructure seems to still be using Node v4.

I assume they'll be updating it but that was true as of last week.

Too bad half the modules on npm wont work in 5+ And I don't blame people for not fixing breaking changes every third month. Ohh the module has less then 100 collaborators !? I better not use it then. Ohh it has not been updated within the last month ? Better not use it. The cool project that required beta version of node, now half a year later it's too old. The best part of nodej is code reuse. Not code re-write! /rant

A bit overblown, don't you think?

I use node 5+ since like forever. Next to every npm-module works for me. And if not, a node downgrade does not help.

I think that person meant npm 5 perhaps?

Good point. Indeed npm breaks a lot of things also for me.

Like...?

Which still isn't true, so I have no idea what they are talking about.

The problem is with the ABI and libuv. It's very hard to debug and fix the problems if you do not know C++

I do a lot of systems programming in NodeJS and are depending on those modules to access platform API's.

That’s surely a problem with C++ and OS tooling rather than npm tho...?

The problem is NodeJS semver major, eg breaking changes. And the nodejs modules stop working. And the high frequency of semver major makes it hard to keep up. If you are lucky the module is maintained at all that is.

Reply on news.ycombinator.com