Support Node 4.2

[khwerhahn]

Upgrade to node 4? https://new.nodejs.org/en/

[kingcody]

We are investigating this, currently there are some broken deps that need to update. We'll see how things pan out over the next couple of weeks.

[Awk34]

This might as well serve as the tracking issue for it though.

[Awk34]

The one that I'm watching is gulp-sass, since it depends on node-sass, which is using pangyp instead of node-gyp and is causing issues. This has to do with the gulp branch that I'm working on for 3.0.0.

[Awk34]

Seems like this is resolved in node-sass.

[Awk34]

#1280 Adds Node 4.0.0 to the TravisCI targets

[corporationsruleyourmom]

Good info here pretty excited about seeing the advantages of Node.js and io.js working together

[macneib]

FYI: node 4.2.0 will be the LTS release

[Awk34]

@macneib source?

[macneib]

@Awk34 nodejs/node#3000 (comment)

also v4.1.2 is a critical update and that's available now. https://nodejs.org/en/blog/release/v4.1.2/

The Node team is moving at full blast these days, which is both awesome and super stressful because It's near impossible for my group to keep up. 4.2.0 will hopefully give everyone a break and let the downstream maintainers and end users catch up.

[macneib]

4.2.0 LTS now released
https://twitter.com/nodejs/status/653644449025814528

[vartana]

Did this get resolved? If not what is the eta?

[Awk34]

The issue will be closed when resolved. No ETA. #1400 has to pass.