Page MenuHomePhabricator

[RFC] RESTBase: Drop support for node 0.10 (and 0.12?)
Closed, ResolvedPublic

Description

0.10 is basically EOL (absolute EOL scheduled for 2016-10-01). We are running the stable & maintained 0.4.x series in production.

We should consider dropping 0.10 and possibly 0.12 support soon. Advantages of doing so:

  • No need to deal with 0.10 test flakyness.
  • Ability to use modern ES6 features supported in Node 4, like const, let, classes etc.

An alternative would be to compile modern JS to 0.10 using babeljs, but maintaining such a setup takes time & it is not clear that the cost / benefit ratio is sensible.

See also

Event Timeline

GWicke renamed this task from [RFC] RESTBase: Drop support for node 0.10 to [RFC] RESTBase: Drop support for node 0.10 (and 0.12?).May 2 2016, 9:05 PM
GWicke updated the task description. (Show Details)

I'm up for dropping both 0.10 and 0.12 and starting to use ES6 everywhere. Change-prop shows it's really nice to use it

I'm for it, but am not at all aware whether that impacts anybody outside of WMF. Let's find out before deciding?

@mobrovac: Would you mind starting a discussion, or otherwise find out if there are hyperswitch or RB users on 0.10?

See also https://github.com/wikimedia/hyperswitch/pull/57 for a related discussion about dropping core-js in hyperswitch.

A basic first step for questions like this is to see what the major distros (especially the LTS ones) are providing for node versions. As a point of data, looks like CentOS 7 is providing 0.10.46. On the other hand, we usually end up installing a local node anyway, so it won't affect us very much.

Pchelolo claimed this task.

Code related to RESTBase has been updated to use ES6 features, so support was dropped. Resolving the task.