Closed
Bug 1211535
Opened 9 years ago
Closed 8 years ago
[Meta] Raptor build
Categories
(Firefox OS Graveyard :: Gaia::PerformanceTest, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Eli, Assigned: rwood)
References
Details
(Whiteboard: [systemsfe])
Introduce build step into Raptor development workflow: - linting - unit/functional testing - ES6 transpilation if no Node.js 4.0+ support - Release automation - more as needed
Assignee | ||
Comment 1•9 years ago
|
||
ES6 transpilation not required, as next Raptor release will require node 4 (es6 native support)
Assignee: nobody → rwood
Status: NEW → ASSIGNED
Comment 2•9 years ago
|
||
There are parts of es6 which are still not supported in node 4, e.g. the spread operator, rest arguments, destructuring assignments, class and super. It might still be useful to consider babel for transpilation.
Reporter | ||
Comment 3•9 years ago
|
||
Good point. We can come back to transpilation as our lowest priority if we can fit it in for this timeframe, mostly because I *really* want destructuring assignment. Class and super most likely wont be permitted in the mozilla-raptor repositories.
Assignee | ||
Updated•8 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•