dylang / grunt-notify Goto Github PK

I'd like to use the notification bits for a project I'm working on outside of grunt. Do you plan on making notify an abstracted module?

e.g.

notify = require 'node-notify'

notify
  message: "Test"
  system: "growl"

notify 'test' # detects available notifier

https://github.com/tjanczuk/wns

Idea via @branneman http://www.reddit.com/r/node/comments/1oco22/termy_programmatically_send_os_x_notifications_in/ccs0h5l

I love it, but I'd like to be able to do npm install -g grunt-notify and not have to install it as a dependency on every project I'm on... mostly because I work with a lot of other devs on projects, and they may not all want the popup... thoughts?

sorry !!!

Is it me or the screenshot & notice about the icons are out of date
Because :

I'm posting this issue to let you know that we will be publishing Grunt 0.4 on Monday, February 18th.

If your plugin is not already Grunt 0.4 compatible, would you please consider updating it? For an overview of what's changed, please see our migration guide.

If you'd like to develop against the final version of Grunt before Monday, please specify "grunt": "0.4.0rc8" as a devDependency in your project. After Monday's release, you'll be able to use "grunt": "~0.4.0" to actually publish your plugin. If you depend on any plugins from the grunt-contrib series, please see our list of release candidates for compatible versions. All of these will be updated to final status when Grunt 0.4 is published.

Also, in an effort to reduce duplication of effort and fragmentation in the developer community, could you review the grunt-contrib series of plugins to see if any of your functionality overlaps significantly with them? Grunt-contrib is community maintained with 40+ contributors—we'd love to discuss any additions you'd like to make.

Finally, we're working on a new task format that doesn't depend on Grunt: it's called node-task. Once this is complete, there will be one more conversion, and then we'll never ask you to upgrade your plugins to support our changes again. Until that happens, thanks for bearing with us!

If you have any questions about how to proceed, please respond here, or join us in #grunt on irc.freenode.net.

Thanks, we really appreciate your work!

Is there any way to specify / choose the platform ?
E.g.:

notify_hooks: {
    options: {
      platform: 'growl'    }
  }

I'm trying to extend this for mail notifications but NodeJs is not quite my comfort zone :)

Any help would be greatly appreciated !

I'm using [email protected], [email protected] and [email protected] on Mac OS X 10.9 (and the notification center).

When making grunt watch I get this error:

Running "watch" task
Waiting...

fs.js:427
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^
Error: EMFILE, too many open files '/Users/emagnier/Projects/Website/node_modules/grunt-notify/lib/platforms/growl-notify.js'
    at Object.fs.openSync (fs.js:427:18)
    at Object.fs.readFileSync (fs.js:284:15)
    at Object.Module._extensions..js (module.js:473:44)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at choosePlatform (/Users/emagnier/Projects/Website/node_modules/grunt-notify/lib/notify-lib.js:27:22)
    at postNotification (/Users/emagnier/Projects/Website/node_modules/grunt-notify/lib/notify-lib.js:70:22)
    at notifyHook (/Users/emagnier/Projects/Website/node_modules/grunt-notify/lib/hooks/notify-fail.js:104:12)

I'm also using Sails.js, and when it load the "watch" task (via the sails lift command) I also get an error:

verbose: Grunt :: Running "notify:server" (notify) task
verbose: Grunt :: Running "watch" task
verbose: Grunt :: Waiting...
error: Grunt :: 

error: Grunt :: child_process.js:935

error: Grunt ::     throw errnoException(process._errno, 'spawn');

error: Grunt :: ^

error: Grunt :: Error: spawn EMFILE
    at errnoException (child_process.js:988:11)
    at ChildProcess.spawn (child_process.js:935:11)
    at exports.spawn (child_process.js:723:9)
    at module.exports (/Users/emagnier/Projects/Website/node_modules/grunt-notify/lib/util/spawn.js:13:15)
    at Object.notify (/Users/emagnier/Projects/Website/node_modules/grunt-notify/lib/platforms/notification-center.js:65:3)
    at postNotification (/Users/emagnier/Projects/Website/node_modules/grunt-notify/lib/notify-lib.js:91:25)
    at notifyHook (/Users/emagnier/Projects/Website/node_modules/grunt-notify/lib/hooks/notify-fail.js:104:12)
    at Object.watchForContribWatchWarnings (/Users/emagnier/Projects/Website/node_modules/grunt-notify/lib/hooks/notify-fail.js:32:16)
    at Object.hooked [as writeln] (/Users/emagnier/Projects/Website/node_modules/grunt/node_modules/hooker/lib/hooker.js:108:32)
    at Object.grunt.fatal.grunt.fail.fatal (/Users/emagnier/Projects/Website/node_modules/grunt-contrib-watch/tasks/lib/taskrunner.js:322:17)

I'm not sure if these errors come from the notify or the watch task.
In the error messages there is a couple mentions of grunt-notify, but if I downgrade the watch plugin to 0.4.4 the problem disappears...

homepage link on https://github.com/dylang/grunt-notify 404s

Noticed this a while back... Wondering if anyone else has?
(osx 10.8.4 | grunt-notify 0.2.7)

Hi,

I'm trying to configure the grunt-notify on my Gruntfile.js, but without success.
Tested on Ubuntu with the Notify-Send and Windows 8 with Growl for Windows and Snarl, both do not work.
The command I am running is: grunt notify
In the terminal only displays the message: Done, without errros
Below is my Gruntfile test.

module.exports = function(grunt) {

    // Load all tasks
    require('matchdep').filterDev('grunt-*').forEach(grunt.loadNpmTasks);

    grunt.initConfig({
        notify: {
          test: {
            options: {
              message: "Test"
            }
          }
    });

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

Thanks!

Right now, the notification fades out way to quick when there is more than one message; not giving enough time to read the message. This was my case when getting notifcations from Karma:

Warning: Task "karma:ci" failed. Use --force to continue.

Aborted due to warnings.

First message seems to be overridden by the second not giving enough time to read it.

We don't need notifications on our CI server. grunt notify should silently continue to the next task instead of silently failing if notify-send isn't found.

dhcp174-64-red:context grishaev$ grunt notify:watch
Running "notify:watch" (notify) task
Warning: Command failed: /bin/sh: /Users/grishaev/Yandex: No such file or directory
 Use --force to continue.

Aborted due to warnings.
dhcp174-64-red:context grishaev$ pwd
/Users/grishaev/Yandex Direct/context

Gruntfile.js:

        notify: {
            watch: {
                options: {
                    title: 'Yandex Direct',
                    message: '"_context*" files are built'
                }
            }
        },

It would be nice to provide a brief summary of how grunt-notify uses the two hooks it is provided with: fail and jshint. How are developers to know how to make grunt-notify work with their own tasks?

I have the grunt file set up and I have Snarl installed, but no matter what I do, I cannot get a notification to display.

module.exports = function(grunt) {

    // Project configuration.
    grunt.initConfig({
        pkg: grunt.file.readJSON('package.json'),
        sass: {                              // Task
            dist: {                            // Target
                options: {                       // Target options
                    style: 'expanded'
                },
                files: {                         // Dictionary of files
                    './theme/style.css': './theme/style.scss'
                }
            }
        },
        typescript: {
            base: {
                src: ['./js/*.ts'],
                dest: './js',
                options: {
                    module: 'commonjs', //or commonjs
                    target: 'es5', //or es3
                    sourceMap: true
                }
            }
        }
    });

    grunt.loadNpmTasks('grunt-contrib-sass');
    grunt.loadNpmTasks('grunt-typescript');
    grunt.loadNpmTasks('grunt-notify');

    // Default task(s).
    grunt.registerTask('default', ['sass', 'typescript']);


};

For the same project with the same configuration (I only use "grunt.loadNpmTasks('grunt-notify');") notifications work fine when I run the watch task in linux but not when I run it in windows (7).
The below error appear :
Loading "notify.js" tasks...ERROR
TypeError : Arguments to path.join must be strings
Loading "notify_hook.js" tasks...ERROR
TypeError : Arguments to path.join must be strings

Im running OSX Mountain Lion and I love the concept of grunt-notify!

It works nice with reporting jshint fails and mocha test errors. Unfortunately, notification messages overrides each other, so I only see the last notification. Since grunt always prints the message "Aborted due to warnings." when something failed, this is always the notification I see. The other notifications (the ones that I actually would like to see) I only see for a split second.

So I wonder if you could make an option to not notify the standard "Aborted due to warnings" notification? Or even better make the notifications not override each other, but I guess this is an OS X issue..

Thanks

It seems that only my JSHint task displays detailed error info in the notification message. If I have errors in SASS or CoffeeScript files, the notification only says "Error".

Furthermore, grunt-notify does not respect any custom title in my notify_hooks task in my project's Gruntfile.coffee – it just uses the name from my project's package.json:

notify_hooks:
  options:
    enabled: true
    title: 'Project Name'

The (relavant) output of $ grunt -v:

Running "sass:dist" (sass) task
Verifying property sass.dist exists in config...OK
Files: assets/sass/main.scss -> assets/css/main.min.css
Options: style="compressed", compass, sourcemap
Writing assets/css/main.min.css...OK
WARNING: $columns must be a unitless number or list of unitless numbers. Current value [number]: 16aaa
         on line 28 of /Users/montchr/.rvm/gems/ruby-2.1.1@ttncutnado/gems/susy-2.0.0/sass/susy/math/_validation.scss, in `pre'
         from line 12 of assets/sass/pages/_layout.scss
         from line 195 of assets/sass/main.scss

WARNING: $columns must be a unitless number or list of unitless numbers. Current value [number]: 16aaa
         on line 28 of /Users/montchr/.rvm/gems/ruby-2.1.1@ttncutnado/gems/susy-2.0.0/sass/susy/math/_validation.scss, in `pre'
         from line 12 of assets/sass/pages/_layout.scss
         from line 195 of assets/sass/main.scss

Syntax error: Invalid null operation: "0 plus null".
        on line 46 of /Users/montchr/.rvm/gems/ruby-2.1.1@ttncutnado/gems/susy-2.0.0/sass/susy/math/_columns.scss, in `pre'
        from line 12 of assets/sass/pages/_layout.scss
        from line 195 of assets/sass/main.scss
  Use --trace for backtrace.
File "assets/css/main.min.css" created.
>> [grunt-notify] growl: growlnotify wasn't found. If you were hoping to use Growl, make you sure you have their command line script called Growlnotify. Mac: http://growl.info/downloads or Windows: http://www.growlforwindows.com/gfw/help/growlnotify.aspx and put it in your path. You should be able to type growlnotify --version and get something back.
>> [grunt-notify] IS_WINDOWS: false
>> [grunt-notify] PROGRAM_FILES: undefined
>> [grunt-notify] PROGRAM_FILES_X86: undefined
>> [grunt-notify] fullPathToApplication: false
>> [grunt-notify] snarl: Snarl not available for this OS.
>> [grunt-notify] os: Darwin
>> [grunt-notify] version: 13.1.0
>> [grunt-notify] IS_MAC: true
>> [grunt-notify] MOUNTAIN_LION: true
>> [grunt-notify] notification_center: Will use Notification Center
>> [notification-center] cmd: /Users/montchr/Sites/vvv-nginx/www/ttn-cutnado/htdocs/web/app/themes/cutnado/node_modules/grunt-notify/bin/Grunt.app/Contents/MacOS/Grunt
>> [notification-center] args: -title cutnado -message Error
Warning:  Use --force to continue.

Aborted due to warnings.

I see that on line 44 of lib/hooks/notify-jshint.js, the grabErrors function handles the JSHint error message.

Why aren't there any detailed error messages or hooks for other common Grunt plugins? If it's not supported out of the box, are there any reliable resources for these hooks out there?

1. I have installed Growl for windows: http://www.growlforwindows.com/
2. With grunt installed before i have installed growl-notify using npm command
3. Configure it properly and run grunt
4. When some task fails a beep sound

Any idea? Any window users has made it run?

Thanks for all.

Sometimes a small change can lead to a huge number or jshint errors, resulting in a succession of notifications for just a small error.
Though the jshint parsing is cool, it would be nice to optionally prevent it (from the Gruntfile) from notifying each error and just give an overall 'jshint failed' message.

I unhooked your hook and put back the original to get this result.

Great plugin, thanks for sharing.

I am working on getting message types working for growl on windows. I want to use this issue document, and collaborate with anyone interested in adding type support for other platforms.

• add additional type parameter to options
• pass application name (this may already be supported)
• register application at the start of grunt

Working branch: https://github.com/jmaxxz/grunt-notify/tree/messageTypes

Using xubuntu 12.04 (xfce 4) no alert messages from failed karma unit tests.

"grunt-karma": "~0.6.2"

On this platform using grunt-contrib-jshint notify message work fine.

"grunt-contrib-jshint": "~0.6.4"

Both jshint and karma run on file changes.

Awesome plugin - would love to get notity message on failed karma unit tests.

Sample karma cmd line output (no notify message):

INFO [watcher]: Changed file "/projects/demo/public/js/controllers/articlesCtrl.spec.js".
OK
>> File "public/js/controllers/articlesCtrl.spec.js" changed.

PhantomJS 1.9.2 (Linux) myApp1 controller ArticlesCtrl $scope.locateTo should locate to a new URL FAILED
        Expected '/articles/528449d0699c899935000002' to be '/articles/528449d0699c899935000002a'.
PhantomJS 1.9.2 (Linux): Executed 25 of 25 (1 FAILED) (0.55 secs / 0.159 secs)

I get no notification on error on OS X 10.9.2 and grunt-notify 0.2.20.

My package.json:

{
    "name": "polona-gui",
    "version": "2.1.0-pre",
    "devDependencies": {
        "connect-modrewrite": "0.5.11",
        "findup-sync": "0.1.3",
        "grunt": "0.4.4",
        "grunt-angular-templates": "0.5.3",
        "grunt-autoprefixer": "0.7.2",
        "grunt-check-dependencies": "0.3.1",
        "grunt-contrib-clean": "0.5.0",
        "grunt-contrib-concat": "0.4.0",
        "grunt-contrib-connect": "0.7.1",
        "grunt-contrib-copy": "0.5.0",
        "grunt-contrib-htmlmin": "0.2.0",
        "grunt-contrib-jshint": "0.7.2",
        "grunt-contrib-sass": "0.7.3",
        "grunt-contrib-uglify": "0.4.0",
        "grunt-contrib-watch": "0.6.1",
        "grunt-csso": "0.6.1",
        "grunt-ddescribe-iit": "0.0.4",
        "grunt-defs": "0.6.1",
        "grunt-jscs-checker": "0.4.1",
        "grunt-jsonlint": "1.0.4",
        "grunt-karma": "0.8.2",
        "grunt-merge-conflict": "0.0.2",
        "grunt-newer": "0.7.0",
        "grunt-ng-annotate": "0.0.4",
        "grunt-notify": "0.2.20",
        "grunt-protractor-runner": "0.2.4",
        "grunt-rev": "0.1.0",
        "grunt-shell": "0.6.4",
        "grunt-usemin": "2.1.0",
        "image-size": "0.2.3",
        "jit-grunt": "0.3.2",
        "jscs-trailing-comma": "0.0.5",
        "karma": "0.12.3",
        "karma-chrome-launcher": "0.1.3",
        "karma-coverage": "0.2.1",
        "karma-firefox-launcher": "0.1.3",
        "karma-jasmine": "0.2.2",
        "karma-junit-reporter": "0.2.1",
        "karma-ng-json2js-preprocessor": "0.0.6",
        "karma-opera-launcher": "0.1.0",
        "lodash": "2.4.1",
        "mime": "1.2.11",
        "protractor": "0.21.0",
        "randomstring": "1.0.3",
        "time-grunt": "0.3.1"
    }
}

I just update & now I got this error for a task using assemble

Object html/pages/board.html,html/pages/demo.html has no method 'replace'

When I remove grunt.loadNpmTasks('grunt-notify');, my task works like a charm. Any clue ?

And this is strange, because it registered earlier

Any help?

There is a new option in [email protected] called force:

Set force to true to report JSHint errors but not fail the task.

With this enabled, any errors will not channel through to grunt-notify.

Is there any way we can channel errors from a task that does not always fail, but display errors, such as this one?

Is it possible to add an option to specify a custom icon ?

It's more a question than a issue, but i wonder if it's possible to send notifications remotely.

I code on Windows & OSX, but my files are stored/edited on a remote ubuntu server through a shared folder with samba . I launch "grunt watch" through ssh. And indeed i hear a simple "bip" sent by the terminal when something went wrong

Is there a way to send notification for example from ubuntu to Windows in this setup ?

Regards

Warning is not displayed through grunt-notify, when grunt-contrib-watch is used with spawn:false option.

As @vict-shevchenko notices:
grunt-watch suppresses error and warning events, so in command line you'll see only
Warning:
but not
Warning: Use --force to continue.Aborted due to warnings. and notification miss this.

Thanks for a really useful tool. I've been using it along with ember-app-kit to get notification of problems with my build.

One problem is that I get a bunch of random ">> No tasks were registered or unregistered" messages. The message is triggered by the interaction of grunt-notify and ember-app-kit, the messages don't occur when either project is used alone. The error message comes from grunt/lib/grunt/task.js when loadTask is called but I haven't figured out what is calling loadTask. I suspect it's to do with the way ember-app-kit loads it's configuration and tasks (via something called load-grunt-config).

To reproduce you can do the following:

git clone [email protected]:stefanpenner/ember-app-kit.git
cd ember-app-kit
npm install
grunt dist

You will see a whole bunch of information as ember-app-kit builds a version of the app. Note that there are no warnings or errors.

Now we'll install grunt-notify and run the command again:

npm install grunt-notify --save-dev
grunt dist

Notice that the warning ">> No tasks were registered or unregistered" is triggered multiple times (in the console and in Notification Centre - I'm on OSX Mavericks).

Any idea what is going wrong here?

Would this fit into the goal of this project ? Would this be feasable ? I would be able to uninstall Snarl 😄

the only debug message from grunt about notify is Running "notify:default" (notify) task.

My configuration looks like this:

  grunt.initConfig
    notify:
      default:
        options:
          message: 'Compiled Successfully'

grunt.loadNpmTasks 'grunt-notify'

 grunt.registerTask 'default', [
    'clean'
    'coffee'
    'commonjs' 
    'concat:scripts'
    'concat:styles'
    'notify:default'
  ]

Snarl is an open-source alternative to Growl For Windows.

Support would be highly appreciated and shouldn't be too complicated, see the Developer Guide.

The easiest way is probably to use the heysnarl-tool, which comes with the default Snarl installation (in the tools folder).

It is as easy as this:

heysnarl "register?app-sig=app/TimerApp&title=TimerApp&keep-alive=1"
heysnarl "notify?app-sig=app/TimerApp&title=Hello, World&text=HeySnarl demo"

The docs say, you should register every time you send a notification. The keep-alive param prevents snarl from unregistering an application for house-keeping purposes, but the param shouldn't be needed if you register every time you send a notification (i just hacked that together, before i knew it was better to re-register every time...).

Thanks!

I don't get notification when test fails, is it normal? I'm on OSX.

cannot reopen #48 ,open a new ticket here.

I am using OSX 10.9 and get some problem when using grunt-karma.
with the following options:
singleRun:true --notifiy works
autorun:true --notify doesn't work

simpleRun:true is not a good solution since it will need to launch the browser for every run.

I'm using notify-send on gnome-shell and find that for every grunt-watch retry it spawns a new notification... the result is a lot of duplicate notifications.

Is there a way to avoid sending a notification if its content matches that of the previous one? or something like this...

Logo does not appear in Growl neither in Snarl on Windows 8. The problem probably is due to how node 'path.resolve' works, making it useless in a command line context. Probably, switching backslashes to forward lashes will fix the issue.

It appears as though Mavericks now requires a sender in order to display the message. Note the issue at julienXX/terminal-notifier#63

Errors like the one on the following screenshot don't generate notification.
I have tried with both mountain lion and growl, neither shown any notification.

http://cl.ly/image/251O2H1K2s0y

Could you help?

Cheers.

This is my setup:

notify_hooks: {
  options: {
    enabled: true,
    max_jshint_notifications: 5,
    title: 'My Project' 
  }
},
notify: { // doesn't work..
  completed: {
    options: {
      message: 'Task completed!'
    }
  }
},

and I call it like this notify:completed in my registered tasks. In the console it says that it was ran, but the Snarl notification doesn't pop up. But JSHint works.

Hey there. First off, great package, at least in theory! I am having some trouble getting notifications to appear.

I was wondering if it was I was possibly doing something wrong, or if it's a system issue.

I have had a few issues with Growl and Notification Center in the past, so it could be my system, but when I ran grunt test from the project master, the notification worked.

Is this designed to only show notifications on errors? I was hoping to get a little more granular control over it and show it on success of certain tasks (e.g. concat of a large vendor library when I make changes, etc).

Is there a way to override the Notification engine preference? I was thinking of just sidestepping Growl altogether, possibly.

Basic snippet from my Gruntfile:

# notify
notify:
  styl:
    options:
      message: "Stylus compiled."
  coffee:
    options:
      title: "Scripts compiled and uglified."
      message: "Coffee compiled."

Then on watch:

grunt.initConfig

watch:
  options:
    spawn: true

  prod:
    files: ["**/*"]
    tasks: ["concurrent:prod"]

  coffee:
    files: ["**/*.coffee"]
    tasks: ["coffee", "concat", "uglify", "notify:coffee"]

  stylus:
    files: ["public/stylesheets/**/*.styl"]
    tasks: ["stylus", "concat:app", "notify:styl"]

Maybe there's some configuration step(s) I'm missing?

Only one adjustment in Release History: would be not "Dec 2012" instead "2013" the first version? ;)

And congratulations on the excellent work! Really like that plugin! xD

I have a simple watch task that runs all my tests when a change is detected on my source code. Not sure why, but after the watch finish running all my tests and a failure is detected ... the expected notification does not show up.

the setup of my watch is:

watch: {
    scripts: {
        files: ['js/src/**/*'],
        tasks: ['test'],
        options: {
            spawn: false
        }
    }
}

and for the notification I am using the basic default config.

Any help or hint here would great,

Thanks,

Hi,

I am not sure if the problem comes from your module or from grunt-contrib-watch. I use the latest version of grunt-contrib-less, grunt-contrib-watch and grunt-notify on Mac OS 10.8.

If I run manually grunt less with a malformed .less file, I will see the notification 👍
But if I launch grunt watch and then break a .less file, I will see the warning in the console but no notification.

Running on OSX 10.9.2 using Growl and Growl Notify.
Notifications of warnings work but if no error I can't get a success message to display using watch. The message does display if I just run grunt.

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

  grunt.initConfig({
    jshint: {
      options: {
        jshintrc: '.jshintrc'
      },
      all: [
        'Gruntfile.js',
        'assets/js/*.js',
        '!assets/js/scripts.min.js'
      ]
    },
    less: {
      dist: {
        files: {
          'assets/css/main.min.css': [
            'assets/less/app.less'
          ]
        },
        options: {
          compress: true,
          // LESS source map
          // To enable, set sourceMap to true and update sourceMapRootpath based on your install
          sourceMap: false,
          sourceMapFilename: 'assets/css/main.min.css.map',
          sourceMapRootpath: '/app/themes/roots/'
        }
      }
    },
    uglify: {
      dist: {
        files: {
          'assets/js/scripts.min.js': [
            'assets/js/plugins/bootstrap/transition.js',
            'assets/js/plugins/bootstrap/alert.js',
            'assets/js/plugins/bootstrap/button.js',
            'assets/js/plugins/bootstrap/carousel.js',
            'assets/js/plugins/bootstrap/collapse.js',
            'assets/js/plugins/bootstrap/dropdown.js',
            'assets/js/plugins/bootstrap/modal.js',
            'assets/js/plugins/bootstrap/tooltip.js',
            'assets/js/plugins/bootstrap/popover.js',
            'assets/js/plugins/bootstrap/scrollspy.js',
            'assets/js/plugins/bootstrap/tab.js',
            'assets/js/plugins/bootstrap/affix.js',
            'assets/js/plugins/*.js',
            'assets/js/_*.js'
          ]
        },
        options: {
          // JS source map: to enable, uncomment the lines below and update sourceMappingURL based on your install
          // sourceMap: 'assets/js/scripts.min.js.map',
          // sourceMappingURL: '/app/themes/roots/assets/js/scripts.min.js.map'
        }
      }
    },
    version: {
      options: {
        file: 'lib/scripts.php',
        css: 'assets/css/main.min.css',
        cssHandle: 'roots_main',
        js: 'assets/js/scripts.min.js',
        jsHandle: 'roots_scripts'
      }
    },
    watch: {
      less: {
        files: [
          'assets/less/*.less',
          'assets/less/bootstrap/*.less'
        ],
        tasks: ['less', 'version']
      },
      js: {
        files: [
          '<%= jshint.all %>'
        ],
        tasks: ['jshint', 'uglify', 'version']
      },
      livereload: {
        // Browser live reloading
        // https://github.com/gruntjs/grunt-contrib-watch#live-reloading
        options: {
          livereload: true
        },
        files: [
          'assets/css/main.min.css',
          'assets/js/scripts.min.js',
          'templates/*.php',
          '*.php'
        ]
      }
    },
    clean: {
      dist: [
        'assets/css/main.min.css',
        'assets/js/scripts.min.js'
      ]
    },

      notify: {

          done: {
              options: {
                  message: 'Success!' //required
              }
          }
      }

  });


  // Load tasks
  grunt.loadNpmTasks('grunt-contrib-clean');
  grunt.loadNpmTasks('grunt-contrib-jshint');
  grunt.loadNpmTasks('grunt-contrib-uglify');
  grunt.loadNpmTasks('grunt-contrib-watch');
  grunt.loadNpmTasks('grunt-contrib-less');
  grunt.loadNpmTasks('grunt-wp-version');
  grunt.loadNpmTasks('grunt-notify');

  grunt.option('force', true);

  // Register tasks
  grunt.registerTask('default', [
    'clean',
    'less',
    'uglify',
    'version',
    'notify:done'
  ]);
  grunt.registerTask('dev', [
    'watch'
  ]);

};

grunt-contrib-watch is replacing the grunt.warn, grunt.fail.warn, etc functions that grunt-notify hooks into for showing notifications.

See: gruntjs/grunt-contrib-watch#232

I may create a workaround where I hook into grunt.log.writeln and use the messages that grunt-contrib-watch is printing as the notify message.

Hi, I'm having a problem with Compass task errors, It just shows a "?" in the notification description. In less compile errors seems to work right.

Is it possible to have an option like:

icon: "img/icon.png"

To ovverride the default grunt icon? :)