Command line support about time-grunt HOT 5 CLOSED

For it to know the time each task takes you would have to specify your run script as arguments to timegrunt:

$ timegrunt eslint mocha 'uglify src/app.js > dist/app.js'

from time-grunt.

That's not really ideal though because it would mean one massive line of tasks / build configurations.

Ideally it would be nice if this plugin was split into two repositories; time-node and time-grunt. The time-node would be responsible for exposing an api to log .start and .end events for tasks, plus rendering (and expose CLI). The grunt task would just call api methods on it. That gives full flexibility in how you want to use the timer; in grunt, through CLI, or even by node thru the api itself. What do you think?

from time-grunt.

Similar to how a lot of profiler apps works -- just .start('name of task') then .end('name of task') and it can calculate how long it took. Similar thru the CLI it would be, with any mixture of tasks etc:

timegrunt --start 'building css'
timegrunt --end 'building css'
timegrunt --render

from time-grunt.

This is kind of how I envisaged using it:

"scripts": {
    "build": "timegrunt --start 'building...' && npm run clean && npm run js && npm run css",

    "postbuild": "timegrunt --render",

    "clean": "timegrunt --start 'clean' && rimraf public/dist && timegrunt --end 'clean'",

    "js": "timegrunt --start 'js' && mkdirp public/dist/js && browserify resources/assets/js/site.js -o public/dist/js/app.js && timegrunt --end 'js'",

    "css": "timegrunt --start 'css' && lessc resources/assets/less/site.less public/dist/css/site.css && timegrunt --end 'css'"
}

from time-grunt.

Closing as this project is deprecated because Grunt is no longer actively maintained, so it doesn't make sense for me to maintain this project either.

from time-grunt.