![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
grunt-timer
Advanced tools
Times the duration of each of your grunt tasks automatically and outputs the execution time in milliseconds to the console after each task (or optionally, at the end). It also logs the total time for all logged tasks.
grunt-timer.js times the duration of each of your grunt tasks automatically and outputs the execution time in milliseconds to the console after each task. It also logs the total time for all logged tasks at the end.
npm install grunt-timer ## --save-dev
Add the grunt-timer reference to the very top of your Gruntfile.js:
var timer = require("grunt-timer");
Add the timer init call at the top of the module.exports function:
module.exports = function (grunt) {
timer.init(grunt);
Running "run:500" (run) task
500ms task ran
Task 'run:500' took 502ms
All tasks took 502ms
To use any option, pass an object parameter to your initialise function like so:
module.exports = function (grunt) {
timer.init(grunt, { deferLogs: true, friendlyTime: true, color: "blue" });
If you'd prefer to see a summary of all your task timings at the end of the grunt process, enable this option.
This is useful for the case where you have many grunt tasks, or they generate a lot of output while they are running, and it might be tedious to scroll back through the console to find all the timing messages.
Behaves like deferLogs
but will also do the default inline logging.
This is useful if you want the summary (deferLogs) but a build could timeout, which would means there could be no grunt timer logs.
Enable this if you'd prefer to see the durations reported in a friendly hours/minutes/seconds format, instead of ms.
Task 'jshint:all' took 3 seconds
Enable this if you'd prefer to only see the time all tasks took to complete.
This is useful for having many small, insignificant tasks that would generate considerable output even with deferLogs.
All tasks took 502ms
If supplied, will override default purple for console output.
No color will be output if the grunt --no-color
option is specified.
Array of task aliases to ignore. e.g to stop grunt-timer running with the default task:
module.exports = function (grunt) {
timer.init(grunt, { ignoreAlias: ["default"] });
FAQs
Times the duration of each of your grunt tasks automatically and outputs the execution time in milliseconds to the console after each task (or optionally, at the end). It also logs the total time for all logged tasks.
We found that grunt-timer demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.