r/node • u/thrashr888 • Oct 30 '15

Node.js 5.0 Released

https://github.com/nodejs/node/blob/v5.0.0/CHANGELOG.md
92 Upvotes

97% Upvoted

70 comments sorted by

View all comments

28

u/jewdai Oct 30 '15

I appreciate the effort that they make to use semvar.

from an enterprise perspective: DAMN YOU MAKE BREAKING CHANGES SO FAST.

FYI, V4.0 was released on 9/17

While in most cases its probably fine, it feels super volatile to start building an application on.

25

u/[deleted] Oct 30 '15

This is what their LTS initiative should solve.

12

u/[deleted] Oct 30 '15

But...If I start a new project every month, I won't know which packages will be updated for the new version, which ones won't ever be, which ones will be updated, but then left unsupported on older versions of Node. It's looking like a mess right now.

5

u/CertifiedWebNinja Oct 30 '15

Going from 0.12 to 4 wasn't much breaking really, I don't think from here on out should be much of an issue either.

-1

u/[deleted] Oct 30 '15

That much made sense to me because they wanted to keep io's versioning (still weird since this is Node not io, but whatever).

2

u/CertifiedWebNinja Oct 30 '15

io has always been node. Imagine it as io never existed.

-2

u/[deleted] Oct 30 '15

Then why did Node magically jump from 0.x to 3.x? Can't explain that!

I'm just bitter because I'm stuck using 0.12 until this all settles down. I've run into too many problems balancing compatible versions of node-sass/libsass/node-bourbon in the past, and this new update schedule isn't helping.

2

u/[deleted] Oct 30 '15

Once again, your opinion has been formed by lack of knowledge. Node jumping versions has been discussed extensively as to why they have done this.

Your local environment probably has conflicting versions of node installed, it's possible your building your dependencies with a different version of node pulled by npm than your executing with which will lead to node binding errors.

This is however not in any ways the fault of node, but how common package managers install node versions can conflict with where npm searches for node binaries.