Time-grunt stopped working after updating to grunt 0.4.2

[opus131]

It appears that process.on('exit' ...) is never called. I could fix it by reverting a change in grunt.js (calling process.exit(0); rather than util.exit(0)): https://github.com/gruntjs/grunt/blob/master/lib/grunt.js#L147

So probably a grunt issue?

[sindresorhus]

cowboy/node-exit#4

[vladikoff]

Discussion on a fix for this is in cowboy/node-exit#7

[kud]

Doesn't work at all here. MacOSX 10.9

[Guuz]

Not working here either. Win8.1 and latest version of grunt.

[eddiemonge]

not liminited to windows. Grunt 0.4.2 in general breaks it.

[scottnonnenberg]

Also getting no time-grunt output on Grunt 0.4.2 on OSX 10.9

[binarykitchen]

Thanks for the update @sindresorhus, the times are shown again. But the grunt tasks are never exited now. Always have to CTRL-C to make them quit.

[sindresorhus]

@binarykitchen do you have a testcase? Works fine for https://github.com/sindresorhus/time-grunt/blob/master/Gruntfile.js

[binarykitchen]

Just tested again in the office. Weird. It is working on my office machine (Linux) but not on my home machine (Mac OS X). Will have to check again from home ...

[sindresorhus]

@binarykitchen a5a4592, just npm cache clean and reinstall.

[binarykitchen]

Right, I did that on my office machine and then it worked.

Man, why do I have to clear npm's cache? Shouldn't it invalidate older versions automatically?

[sindresorhus]

@binarykitchen it should, but there's a reason there's a command like that, sometimes it doesn't. A better question is; Why is everything with programming and computers broken?

[binarykitchen]

Haha ... I get it ;) No further questions ... thx!