`time-grunt` doesn't work at all

[Michał Gołębiowski-Owczarek]

Since time-grunt wasn't working in my project, I tried it on an example Gruntfile:

module.exports = function (grunt) {
    'use strict';

    // require it at the top and pass in the grunt instance
    require('time-grunt')(grunt);

    grunt.initConfig();
    grunt.registerTask('default', []);
};

and I still see no output, even in verbose mode:

$ grunt --verbose
Initializing
Command-line options: --verbose

Reading "Gruntfile.js" Gruntfile...OK

Registering Gruntfile tasks.
Initializing config...OK
Loading "Gruntfile.js" tasks...OK
+ default

No tasks specified, running default tasks.
Running tasks: default

Running "default" task

Done, without errors.

I'm on OS X 10.9, the package.json file used for this example is as follows:

{
    "name": "test-app",
    "version": "0.0.0",
    "devDependencies": {
        "grunt": "0.4.2",
        "time-grunt": "0.2.3"
    }
}

[Sebastien Barre]

+1 same issue here on OSX 10.9, even in --verbose mode.

[Sindre Sorhus]

Duplicate of #15

This is an issue with grunt 0.4.2. +1 this thread instead: cowboy/node-exit#7

Temporary workaround is to downgrade to grunt 0.4.1

[Michał Gołębiowski-Owczarek]

@sindresorhus I did look into this ticket and, as I mentioned in #15, it describes a Windows-only issue; the attached test case works fine on my Mac. However, time-grunt doesn't.

Either the test case in cowboy/node-exit#7 is not catching the whole picture or there is, indeed, a bug in time-grunt.

[Sindre Sorhus]

Yup, that testcase is flawed: cowboy/node-exit#7 (comment)

[Michał Gołębiowski-Owczarek]

OK, thanks for info! Subscribed to that other ticket.