Calling devtools is blocking further tasks execution

[roman01la]

Calling devtools task will block execution of any other tasks, if presented.

grunt.task.run([
      'clean:server',
      'bower-install',
      'concurrent:server',
      'autoprefixer',
      'express:dev',
      'devtools',
      'open',
      'watch'
]);

open and watch tasks will never run.

Running globally installed task in another tab in the console is kinda ok, but having the task automatically installed locally and being executed among others with grunt serve is a much more better approach.

[vladikoff]

Thanks for filing the issue. Let me experiment with this.

[roman01la]

This caused by that line of code:

// run forever until the user kills the task
this.async();

What is need to be done is:

var done = grunt.task.current.async();

And call done when the task has finished running all the servers or got an error while running servers, this will notify Grunt to proceed executing further tasks.

Like this:

if (projectPort) {
    // start the server on that port
    server.listen(port, function () {
        grunt.log.ok("Grunt Devtools v" + version + " is ready! Proceed to the Chrome extension.");
        done();
    });
} else {
    grunt.fail.warn("You're running too many Grunt Devtools, please close one.");
    done();
}

This works great for me, no blocking anymore. But, the above code is running out of WebSocket server callback function, which is not really a problem, but still it would be better to call done when the task is really done setting up everything. According to websocket module reference, WebSocketServer constructor doesn't accept a callback function.

[tandrewnichols]

Is this still an active issue? I tried using grunt-bg-shell to wrap the devtools task, as an alternative approach, but the chrome extension never detects it . . . only when I run it directly. So having this work in conjunction with watch would be nice.