In what order does gulp process tasks? -
I am a little confused about the object in which the work of Galpa has been completed. Allow me to explain.
In Gulpfile.js, I have a set of all the necessary functions.
The basic template for each sub work
gulp.task ('compress: customName', function () {return gulp.src (['app / folder / file. Js', 'app / folder / file.js']) .pipe (gp_concat) (' App.customName.min.js')) .pipe (gp_uglify ()) .Pipe (gulp.dest (distDir));} );
Then, I have a task that rules them all
gulp.task ('compress: all', ['compress: CustomName1 ',' compress: customname 2 ',' etc ... '], function () {});
Then another master task runner (using just seconds: all for this example)
gulp.task ('master' ['Compress: all'], function () {return gulp.src ('dist / *. Js') .pip (notify ("compression complete");};
OK ... this is the basic setup ... now to talk about the order that these tasks are completed according to the command line results.
[11:06:44] ] Use of Junkfile C: \ PATH \ to \ PROJECT \ gulpfile.js [11:06:44] Start 'Compressed: customName1' ... [11:06:44] Start 'Contact No: CustomName2 '... [11:06:44] Start' Compressed: CustomName 3 '... [11:06:44] Start' Compression: CustomName 4 '... [11:06:44] Start' Compression: customName5 '... [11:06:44] Start' Compressed: Customname 6 '... [11:06:44] Start' Compressed: Customname 7 '... ... [11:06:44] ] After 108 'Compressed: CustomName 1' MS [11:06:44] 'Compressed: CustomName 6' finished after 93 ms [11:06:44] 'compressed: customname 5' after 132 ms [11: 06:44] 'Compressed: CustomName 4' 11:06:44 after 139 ms 'Compressed: Custom Name 3' [11:06:44] 245A Ended after 'compressed: customname 2' [11:06:44] 381 MS [11: 11] finished 'Compressed: CustomName 7' 06:44] Start 'Compressed: All' ... [11:06] : 44] Ended 'Ess: all' after 6.64 μs [11:06:44] Start 'Master' ... [11:06:44] gulp-notify: [SA example: Gulp Builder] COMPRESSION COMPLETE [11] : 06: 44] After 'finished' master '40' MS
How can 'the master' work to start and start after 'Compressed: All'?
Such a random order?
Why has it been said that 'Master' has been completed in only 40 ms, when all the sub-tasks should be waited, it asks for the answer before fulfilling it himself is?
'Compress: All' after 'Master' to start and get started How can the last thing be done?
Dependencies run before the actual work begins. 'Compressed: All' dependence 'for' master 'is dependent.
Why are the jobs displayed in such a random order?
Dependency is running in parallel i.e. when someone ends up, then depends on that time to complete it.
Why is it said that 'Master' is completed only in 40 ms, does this work invite you to answer before completing it?
Dependency is not included at the time of completion of any work.
"deps - An array of completion and completion of tasks before running your work".
Comments
Post a Comment