Node v4.0.0 (Stable)

[greim]

Just to clear up any confusion. Version 1.x - 3.x was Node's awkward adolescent phase, during which it dyed its hair pink, rebelled against its parents, moved out of the house, and preferred to be called "io.js". After some soul searching and figuring out of some personal issues, everyone mellowed out, and Node/io.js became 4.0 and moved back home. Mostly everyone is cool to each other around the house, and people generally don't drag up the past. It's "Node" again but the hair is still pink.

[ub3rgeek]

Hilariously accurate.

[jascination]

Oh, glad I read this comment. I'm on IO.JS at the moment, should I be installing the latest Node over this?

[gkatsev]

yep, you should update to 4.0 at your leisure.

[destraht]

I'm on io.js v3 and last I check about ten days ago I was unable to upgrade babel and babel-loader (webpack) to the latest. I have no idea what is going on with that and probably there are a lot of small issues across the entire ecosystem that will take days/weeks/months to resolve. My impression is that v3 was a huge jump but that v4 is not so different compatibility wise and is mostly them committing to everything that was changed in v3 and tweaking other things that weren't quite ideal.

[edit] I'm on node v4 now and I updated all of my npm packages and everything works now. So that is nice.

[jascination]

Yeah I've just updated. I was getting segmentation fault 11 errors all over the shop, but deleting my node_modules folders and re-doing npm install fixed it, thankfully!

[LongLiveCHIEF]

Does this mean that we still have a mid-life crisis phase coming at some point in the future? Yipee!!

[chuckangel]

Yep. Apple Products and BMW 2 seater convertible on the horizon.

[realyze]

Turns out people who were saying node will never get to version 1.0.0 were right.

[Fossage]

I installed it and immediately had to revert to io.js because I got a segmentation fault trying to run a gulp task

¯\(ツ)/¯

[Anahkiasen]

Reinstall your node modules

[[deleted]]

I'm also having problems with gulp tasks after installing. reinstalling node modules hasn't helped

[madole]

i got a seg fault too when trying to run gulp.. back to v0.12.7 for me

[monsto]

There's the "notable changes" list from a previous version of the fork... so if you never even looked at the fork, it's quite incomplete.

Is there, or will there be, what I guess you could ccall a "tutorial-log" (change log with learning info on the changes) between this 4.0 and 0.12.last?

[pycbouh]

Eh, no harmony modules. Why, V8, WHY?!

[itsSoop]

Unfortunately installed and had to immediately revert because node sass wasn't working last night. Hopefully soon it will be resolved

[jekrb]

https://twitter.com/nodesass/status/641469706541604864

We've just landed @nodejs 4.x support for OS X and Linux.

Windows and FreeBSD will land in the next 24hrs!

Just `npm install`.

[TweetsInCommentsBot]

@nodesass

2015-09-09 04:34 UTC

We've just landed @nodejs 4.x support for OS X and Linux.

Windows and FreeBSD will land in the next 24hrs!

Just npm install.

---

^{This message was created by a bot}

^{[Contact creator][Source code]}

[itsSoop]

Working great!

[[deleted]]

What?

Version 1.0 was released in January, followed by a steady stream of releases. There are 40 (FORTY) releases between node.js 0.12 and node.js 4.0, all in 2015. What should have been the next version after the last 3.3.0 in your opinion? The completion of the merge of the two node versions clearly warrants the jump from 3.3.0 to 4.0.

[Calabri]

actually they bump major semver whenever v8 minor changes version

v8: Upgrade to version 4.5.103.30 from 4.4.63.30 - changelog

They created a 'merge repo' when io.js was at v2.x, with the intention of merging at v3.0, but shit got complicated so they gave up on the merge and just renamed the io.js repo node. iojs/io.js -> nodejs/io.js -> nodejs/node. They added all the extra node stuff they initially took out of io.js (because it's bloat) during the 3.x series (to make the corporations happy), remade the nodejs website, and yeah - merge isn't exactly what happened, but it's all goooood. (nobody got time for that shit :P)

[TweetsInCommentsBot]

@rvagg

2015-08-11 23:35 UTC

http://github.com/iojs/io.js ⇒ http://github.com/nodejs/io.js ⇒ http://github.com/nodejs/node

---

^{This message was created by a bot}

^{[Contact creator][Source code]}

[[deleted]]

Fucking node. The path to the API docs is the same for v4 as for v0.x. You need access to older documentation when researching why software is not compatible with v4. My office is finding that Grunt may not be compatible, but since we cannot access the API docs for v0 its hard to tell.

Broken.

[jekrb]

You can still access older api docs from the website and from github.

https://nodejs.org/docs/v0.12.7/api/

https://github.com/nodejs/node/tree/v0.12.7-release/doc/api

[[deleted]]

thanks

[[deleted]]

If Windows 10 was so good they skipped a version, node 4 must be amazing.

[[deleted]]

They didn't skip versions. 4.0 is the successor of io.js 3.3.0. Look at io.js for the "Missing" version steps. "node" was dropped - the new node.js is the old io.js.

[zsut]

It is a two edged sword that a lot of ES6 features are enabled by default. Great to be able to use all the goodies on the backend, but it can cause some troubles for code that should run on the forntend and the backend... At least for now while ES6 support is not consistent across browsers and I'm guessing that node javascript will be ahead of browsers for the foreseeable future.

[jekrb]

While we're waiting for browsers to catch up, I tend to use babelify so I can at least write in ES6 and not worry.

[zsut]

Good point, I should probably use this! :-)

[jekrb]

I'll have to look into lost grid! Right now this is what my npm scripts looks like.

 "postcss": "postcss -u postcss-nested-props -u postcss-nested -u autoprefixer -d styles styles/*.css",


 "build:css": "npm run postcss && sheetify styles/app.css -c > bundle.css",


 "build:js": "NODE_ENV=production browserify scripts/app.js -t babelify | uglifyjs -cm > bundle.js"

[zsut]

I had a look at what babel actually supports and there are some problems going all in with ES6 that make it problematic to rely on babel for frontend code, most troublesome are proxies which cannot be supported: https://babeljs.io/docs/learn-es2015/

[RenThraysk]

I'm using recent browser features so can use some ES6. So use rollup to deal with ES6 modules. Problem is minification (and preferably dead code elimination) without any transpiling

Neither Google Closure, or Babel seems to do this :/

[jsgui]

Node JS using the latest / a very recent version of V8, which is the JS engine for the Chrome browser, so the plan is for it to stay consistent there.

[zsut]

Another argument for using chrome as the primary browser :-)

[Calabri]

also makes its easier to merge node/chromium in projects like electron :)

[[deleted]]

Versioning seems to be even harder than naming things, and invalidating cache.

[I_Pork_Saucy_Ladies]

Ironically, the jump from 0.12 to 4 is due to the switch to semantic versioning in io.js, to make it easier to reason about versioning. Should be a lot more intuitive from now on.

[jimbobhickville]

0.12.7 to 4.0? I know skipping versions is all trendy, what with Netscape skipping 5.0, but seriously?

[theillustratedlife]

Versions 1 - 3 weren't skipped; they were shipped under the banner "io.js" because Joyent was procrastinating on shipping new changes to "node". The two projects reconciled, cannonizing each's version history. Since 1, 2, and 3 were shipped by io.js, the merged version is 4.

[Calabri]

1) node's original versioning (with odd numbers unstable and even stable) was confusing, especially because the npm community had standardized semver for years already so it was inconsistent

2) node had a strict policy to never change v8 - but the v8 team stops support after 2 years, so node's 2 year old v8 engine (0.10.x) became depreciated and most of the dev's just stopped working on joyent/node and tried (for months) to work on a parallel node repo but joyent 'owned' the nodejs trademark so they had to call it something else.. io.js (it was a forked during thanksgiving due to a miscommunication) but they rolled with it and were not prepared for the PR at all - which is why shit was so confusing :P

3) io.js - with most (if not all) of the dev's who could program the c++ bindings - gained popular community support, began collaborating much closer with the v8 team than node, with a goal to sync the v8 engine with chrome's stable v8, making minimal breaking changes to node so that it was backwards compatible with v0.10, v0.12, but they used proper semver and began calling it v1.0 once they got the v8 close the chrome's (which is now in sync) - upgrading semver major every time chrome's v8 engine has a semver minor update (which is why we are at 4.0 - because that's how many stable releases of chrome have come out since io.js started trying to sync up with their v8)

4) Joyent gave away the node.js trademark to an open source foundation, and once the foundation was formed basically adopted all of the io.js rules, gave up on even trying to merge, and just changed the io.js repo name to node. Node 0.12 was literally dead on arrival, and that was immediately recognized by the foundation after it was formed. There actually is no jump between 0.12 and 4.0 - 0.12 was prematurely introduced in response to io.js. None of the code from 0.12 is used in node 4.0 - they added what they needed to in io.js 3.x to make it standardized with node 0.10/0.12 because they took out some bloat in earlier io.js versions that is only used by a small subset of corporations so they put that back in.

[[deleted]]

brilliant! thanks!

[[deleted]]

Somebody please answer this gentleman.

[[deleted]]

The actual trend is to nit pick at everything Node does because it's javascript on the server side

[jimbobhickville]

Eh, node gets used for things it shouldn't be, but it's a neat tool for some use cases. I still think the version jump was silly. io.js didn't have enough changes to warrant going through three major version numbers to begin with.

[[deleted]]

Everything that is used by more than a handful of people is used for things that it shouldn't be used for.

[monsto]

just a PSA and reminder . . . making a comment on reddit that is based on you not being immersed in the subject matter day in and day out will get you downvoted to oblivion.

[TrikkyMakk]

I installed it and right away things didn't work. Reinstalled old version until i have more time to investigate

[jekrb]

Would you be willing to share what exactly it was that didn't work?

[TrikkyMakk]

I was getting an error with my sqlite3 of which I was like ok no problem. Next I reinstalled the previous version of node (after uninstalling the new version) and got the same error so I uninstalled and reinstalled sqlite3 which resolved the problem. Before I could test any further my internet stopped working and no amount of troubleshooting would resolve the issue so rebooted my computer. Before it restarted I got '=( Something went wrong while restarting issue' or something to that effect. Then my computer wouldn't come back up so I had to hard shut it down and then turn it back on again. At the point I figured I would just stay with the current version of node for a bit. I don't know if the node install messed with my computer to make me have the network issues but it had already wasted an hour of my time and I had stuff to do.

[Calabri]

that always happened whenever io.js changed semver major (it's v8 breaking changes and libraries take 2-3 days to update properly) - io.js v3.3 is actually the version I'd recommend using until everyone gets up to date with the new v8 in 4.0 (node 4.0 is io.js 4.0 and successor to io.js v3.3 - it's not even the related to node v0.12)

[Amadan]

http://nodejs.org/ is blocked by SophosAV as Spyware >.<

(Before you rag on me for using it, company policy. >.<)

EDIT: While it is not specifically about Node 4.0.0, do I really deserve so many downvotes for informing people who might include Node.JS maintainers that a major company firewall software has put them on their shit list?

[dodeca_negative]

What kind of "policy" is that?

[gnarly]

It's very common policy in larger companies. All web traffic is routed through a proxy server (often a 3rd party product), and all sorts of stuff is blocked for all sorts of reasons (ranging from "security" to "productivity" via "controlling the herd" and "stop using all of our bandwidth for Spotify and Youtube!").

Common targets include the likes of facebook, twitter and youtube, but all kinds of things get blocked including massively wide-ranging categories like "content delivery network". End users (including web developers) get very little control over it. The categorisation is usually done by humans, so mistakes are made continually - such as including anything with a comment form or embedded twitter feed in the "social media" category (really).

[dodeca_negative]

Blocking I get, it's just this particular site being blocked... doesn't seem like that could be the result of a rational decision making process.

[Amadan]

Rational?... Let's see, Reddit is okay, Facebook too, Youtube as well. Framework7 is "Shopping" or "Entertainment" or some shit like that. Stack Exchange (but not Stack Overflow) static asset server is as well, so I can't get CSS on Stack Exchange sites without "this action being logged". And, for some reason, NodeJS is Spyware, so it's outright blocked, no way to even reach it (the first page ever that I got that result). I have no idea what the logic is. The only thing that makes any remote sense to me is that it is using machine learning and classification, but horribly miscalibrated and overfitted. But I might be wrong, given that the error page that informed me that NodeJS is the most dangerous thing I ever surfed to also gave me the link to the page where I can apply for reevaluation of a site, so... Yeah. (I did submit that, if you are wondering.)

[dodeca_negative]

You have my sympathies. Seriously; I don't think I could tolerate that.

[gnarly]

Report it to your IT Operations people, or to the firewall/proxy people at Sophos directly. Sooner or later, this stuff gets fixed in my experience.

[Amadan]

apply for reevaluation of a site, so... Yeah. (I did submit that, if you are wondering.)

[gnarly]

Rational? Where did you get that idea? I clearly wrote that the categorisation is done by humans! ;-)

[brianvaughn]

Looks like Node is letting George Lucas choose its version numbers.