Content deleted Content added
Visaldatta (talk | contribs) No edit summary |
Visaldatta (talk | contribs) No edit summary |
||
Line 20:
== Need for a Task Runner ==
The main reason why task-runners like gulp and grunt are built on node is because, the basic [[Node Package Manager|npm]] scripts are not efficient when it comes to executing multiple tasks.
Even though a few developers prefer [[Node Package Manager|npm]] scripts to be simple and easy to implement, there are numerous ways where gulp and grunt seem to have an advantage over each other and the default provided scripts.<ref>{{Cite web|url=https://github.com/gulpjs/gulp/blob/master/docs/CLI.md|title=gulpjs/gulp|website=GitHub|access-date=2016-09-23}}</ref> Grunt runs tasks by transforming files and saves as new ones in temporary folders and the output of one task is taken as input for another and so on until the output reaches the destination folder. This involves a lot of [[I/O]] calls and creation of many temporary files. Whereas gulp streams through the file system and does not require any of these temporary locations decreasing the number of I/O calls thus, improving performance.<ref>{{url|https://css-tricks.com/gulp-for-beginners/}}</ref> Grunt uses configuration files to perform tasks whereas gulp requires its build file to be coded. In grunt, each plugin needs to be configured to match its input ___location to the previous plugin’s output. In gulp, the plugins are automatically pipe-lined.<ref>{{url|https://github.com/substack/stream-handbook}}</ref>
== Installation ==
| |||