Confirmed users
429
edits
Gaia/Build/RefactoringToNodejs: Difference between revisions
Jump to navigation
Jump to search
Gaia/Build/RefactoringToNodejs (view source)
Revision as of 03:45, 30 January 2015
, 30 January 2015→Q & A
Ricky Chien (talk | contribs) (→Plan) |
Ricky Chien (talk | contribs) (→Q & A) |
||
| Line 100: | Line 100: | ||
:For node build system, requiring [http://nodejs.org/ Node.js] may be a little bit inconvenient. However, it won't frustrate many users to get started with hacking Gaia since Node provides a great installer for all platforms. After [http://nodejs.org/ Node.js] installed, we can build up new features quickly by NPM and also speed up rewriting Makefile to pure JS. On the other hand, try to rewrite Makefile from scratch in XULRunner seems not so easy. I'm pretty sure and still believe that NPM ecosystem will bring lots of benefits more than XULRunner. | : For node build system, requiring [http://nodejs.org/ Node.js] may be a little bit inconvenient. However, it won't frustrate many users to get started with hacking Gaia since Node provides a great installer for all platforms. After [http://nodejs.org/ Node.js] installed, we can build up new features quickly by NPM and also speed up rewriting Makefile to pure JS. On the other hand, try to rewrite Makefile from scratch in XULRunner seems not so easy. I'm pretty sure and still believe that NPM ecosystem will bring lots of benefits more than XULRunner. | ||
* | * Treeherder or some countries have network issues when pulling packages from NPM. | ||
: | : It should work if we keep hosting our gaia-node-modules mirror to solve such situation. | ||
* In stage 2, buildbot should pre-install proper command tools if we decide to use gulp.js | |||
: We could do so, or we can download gulp every first time build and launch it by relative path. | |||