Node.js 5.0 Released
github.com
Node.js 5.0 Released
1–10 of 132 posts
Re: Node.js 5.0 Released
#2For a person who's not well versed with Node's version history, what's in this update to warrant a jump from version 4 to 5?
Re: Node.js 5.0 Released
#3For a person who's not well versed with Node's version history, what's in this update to warrant a jump from version 4 to 5?
Node now follows Semver. If you look through the changelog, there's more than a dozen changes that are breaking.
Re: Node.js 5.0 Released
#4For a person who's not well versed with Node's version history, what's in this update to warrant a jump from version 4 to 5?
AFAICT there are quite a few changes that are technically breaking changes, but most projects won't be affected. The one big change that I see is mostly hidden: the change from NPM 2 to NPM 3. Make sure you check out the changelog for NPM3: https://github.com/npm/npm/blob/master/CHANGELOG.md#v300-201...
Re: Node.js 5.0 Released
#5Glad to see they've bumped up the V8 version so the spread operator can be used.
Things are really moving along at a good clip since the merge with io.js.
Re: Node.js 5.0 Released
#6For a person who's not well versed with Node's version history, what's in this update to warrant a jump from version 4 to 5?
Node now follows Semver. If you look through the changelog, there's more than a dozen changes that are breaking.
That doesn't answer the question. Node 4.0 was released a month ago. Why are there so many breaking changes in 1 month?
Re: Node.js 5.0 Released
#7I recently looked at using Node for a simple API backend. ES6 seems like it's not there yet, the stability of Node makes me wary. Constant changes seem exhausting to keep up with. For a simple microservice api you don't want to be upgrading it every 3 days. The continuous change doesn't make sense to me. Trying to get up to speed on all the Node.js ecosystem feels exhausting, only to have it change a few weeks later. Maybe someone using this daily for real APIs could comment if this is the case for them?
I ended up opting for Flask and Python 3x instead, couldn't be happier. I had my API up and running within a day with no prior knowledge of Flask and some Python on and off. I've been able to discuss and teach other team members on it who were also able to pick it up easily.
Re: Node.js 5.0 Released
#8For a person who's not well versed with Node's version history, what's in this update to warrant a jump from version 4 to 5?
Node now follows Semver. If you look through the changelog, there's more than a dozen changes that are breaking.
@Touche: because they were introduced by the developers. The type of changes you make dictate the semver, but semver doesn't dictate what changes you can or can't make.
Re: Node.js 5.0 Released
#9Uhh, wait, wasn't nodejs 4.0 only like a month ago? So are there going to be breaking changes every few months now?
Re: Node.js 5.0 Released
#10I recently looked at using Node for a simple API backend. ES6 seems like it's not there yet, the stability of Node makes me wary. Constant changes seem exhausting to keep up with. For a simple microservice api you don't want to be upgrading it every 3 days. The continuous change doesn't make sense to me. Trying to get up to speed on all the Node.js ecosystem feels exhausting, only to have it change a few weeks later.…
No need to always be on the latest version. v4.2 is an LTS branch that will be supported for the next two and a half years.
And with tools like nvm, it's incredibly easy to swap out different versions and go for a test drive.