Here's my Gruntfile and the output.

As you can see in the output, there are a couple of issues related to asynchronous tasks:

1. imagemin is called and the next one es straight ahead. This makes its output appear in the end of the tasks, what's quite messy;
2. build, which is a custom task, is using var done = this.async() and calling done() after finishing the mand; however, this only works correctly if I run the task alone; running it with another tasks makes it run async too;
3. With build running later, jasmine has nothing to test and thus is useless.

Is there a way to fix this behavior?

Here's my Gruntfile and the output.

As you can see in the output, there are a couple of issues related to asynchronous tasks:

1. imagemin is called and the next one es straight ahead. This makes its output appear in the end of the tasks, what's quite messy;
2. build, which is a custom task, is using var done = this.async() and calling done() after finishing the mand; however, this only works correctly if I run the task alone; running it with another tasks makes it run async too;
3. With build running later, jasmine has nothing to test and thus is useless.

Is there a way to fix this behavior?

• javascript
• node.js
• asynchronous
• gruntjs

Share Improve this question Follow asked Mar 31, 2013 at 22:50 igorsantos07igorsantos07 4,69277 gold badges4949 silver badges6565 bronze badges 1

• I never had problems with Grunt's this.async(). Probably a bad side effect of another task? Have you tried your task chain without imagemin? – Sebastian vom Meer Commented Apr 1, 2013 at 12:15

Add a ment  | 

2 Answers 2

Sorted by: Reset to default 9

I believe your problem is with this task:

grunt.registerTask('prepare-dist', 'Creates folders needed for distribution', function() {
            var folders = ['dist/css/images', 'dist/imgs/icons'];
            for (var i in folders) {
                    var done = this.async();
                    grunt.util.spawn({ cmd: 'mkdir', args: ['-p', folders[i]] }, function(e, result) {
                            grunt.log.writeln('Folder created');
                            done();
                    });
            }
    });

If you have multiple folders, both async() and done() will be called multiple times. Async is implemented as a simple flag (true/false) and is meant to be called once. The first done() call allows any follow on tasks to run.

There are many ways to move the calls to async and done out of the loop. A quick google search on something like: nodejs how to callback when a series of async tasks are plete will give you some additional options. A couple of quick (& dirty) examples:

// Using a stack
(function() {
    var work = ['1','2','3','4','5']


    function loop(job) {
        // Do some work here
        setTimeout(function() {
            console.log("work done");

            work.length ? loop(work.shift()) : done();
        }, 500);
    }

    loop(work.shift());

    function done() {
        console.log('all done');
    }
})();

-- or --

// Using a counter (in an object reference)
(function() {
    var counter = { num: 5 }

    function loop() {
        // Do some work here
        setTimeout(function() {
            --counter.num;

            console.log("work done");

            counter.num ? loop() : done();
        }, 500);
    }

    loop();

    function done() {
        console.log('all done');
    }
})();

As you could read in the Grunt documentation:

If a task is asynchronous, this.async method must be invoked to instruct Grunt to wait. It returns a handle to a "done" function that should be called when the task has pleted.

And a short example would be similar to:

// Tell Grunt this task is asynchronous.
var done = this.async();

// Your async code.
fetchData(url).then( data => {
    console.log(data);
    done();
}).catch( error => {
    console.err(error);
    done(false); // false instructs Grunt that the task has failed
});