Confirmed users
478
edits
Gaia/Build/RefactoringToNodejs: Difference between revisions
Jump to navigation
Jump to search
Gaia/Build/RefactoringToNodejs (view source)
Revision as of 06:23, 5 February 2015
, 5 February 2015→Should we choose io.js instead of node.js for developing new build system?: conclusion
Ricky Chien (talk | contribs) (→Plan) |
|||
| Line 146: | Line 146: | ||
== Should we choose io.js instead of node.js for developing new build system? == | == Should we choose io.js instead of node.js for developing new build system? == | ||
In my experience, build scripts doesn't take too many ES6 features, may be able to pass "node --harmony" in node.js environment. So there are no such immediate reasons to choose io.js in current phase. However, io.js provides more complete ES6 features and we'll consider to transfer to io.js in the future. | In my experience, build scripts doesn't take too many ES6 features, may be able to pass "node --harmony" in node.js environment. So there are no such immediate reasons to choose io.js in current phase. However, io.js provides more complete ES6 features and we'll consider to transfer to io.js in the future. We would have to figure out if buildbots can work with multiple Node.js versions (maybe with nvm) before using io.js. | ||
In short, targeting io.js is not the scope of the current plan. | |||