notification plugin for gulp
Package | gulp-notify |
---|---|
Description | Send messages to Mac Notification Center, Linux notifications (using notify-send ) or Windows >= 8 (using native toaster) or Growl as fallback, using the node-notifier module. Can also specify custom notifier. |
Node Version | >= 0.8 |
- Mac OS X: No external installation needed (if Mac OS X 10.8 or higher).
- Linux:
notify-send
/notify-osd
should be installed (On Ubuntu this is installed per default) - Windows: Uses native toaster (if Windows 8 or higher).
- Fallback: Growl: Growl (for Mac, Windows or similar) should be installed.
See node-notifier for details.
First, install gulp-notify
as a development dependency:
npm install --save-dev gulp-notify
Then, add it to your gulpfile.js
:
var notify = require("gulp-notify");
gulp.src("./src/test.ext")
.pipe(notify("Hello Gulp!"));
Or with template
var notify = require("gulp-notify");
gulp.src("./src/test.ext")
.pipe(notify("Found file: <%= file.relative %>!"));
See examples for more or the API section for various inputs.
gulp-notify
passes on the vinyl files
even on error. So if you are
using gulp-plumber
the run
will not break if the notifier returns an error.
If you want to notify on errors gulp-plumber
can be used to not break the run and force you to have to restart gulp.
You can use notify.onError() as the errorHandler for gulp-plumber like this:
gulp.src("../test/fixtures/*")
.pipe(plumber({errorHandler: notify.onError("Error: <%= error.message %>")}))
.pipe(through(function () {
this.emit("error", new Error("Something happend: Error message!"))
}));
A message to notify per data on stream. The string can be a lodash template as it is passed through gulp-util.template.
Type: function(VinylFile)
Vinyl File from gulp stream passed in as argument.
The result of the function can be a string used as the message or an options object (see below). If the returned value is a string, it can be a lodash template as it is passed through gulp-util.template.
If false
is returned from the function the notification won't run.
*Options are passed onto the reporter, so on Windows, you can define Growl host, on Mac you can pass in contentImage, and so on.
See node-notifier for all options*
Default notification values:
- Gulp logo on regular notification
- Inverted Gulp logo on error
- Frog sound on error on Mac.
See also the advanced example.
Type: Boolean
Default: false
If the notification should only happen on the last file of the stream. Per default a notification is triggered on each file.
Type: Boolean
Default: false
If the returned stream should emit an error or not.
If emitError
is true, you have to handle .on('error')
manually in case the notifier (gulp-notify) fails. If
the default false
is set, the error will not be emitted
but simply printed to the console.
This means you can run the notifier on a CI system without opting it out but simply letting it fail gracefully.
Type: String
Default: File path in stream
The message you wish to attach to file. The string can be a lodash template as it is passed through gulp-util.template.
Example: Created <%= file.relative %>
.
Type: Function(vinylFile)
See notify(Function)
.
Type: String
Default: "Gulp Notification"
The title of the notification. The string can be a lodash template as it is passed through gulp-util.template.
Example: Created <%= file.relative %>
.
Type: Function(vinylFile)
See notify(Function)
.
Type: Object
Default: {}
Object passed to the lodash
template, for additional properties passed to the template.
Examples:
gulp.src("../test/fixtures/*")
.pipe(notify({
message: "Generated file: <%= file.relative %> @ <%= options.date %>",
templateOptions: {
date: new Date()
}
}))
Type: Function(options, callback)
Default: node-notifier module
Swap out the notifier by passing in an function. The function expects two arguments: options and callback.
The callback must be called when the notification is finished. Options will contain both title and message.
See notify.withReporter
for syntactic sugar.
If the wait
option is set to true
, the notifier will trigger
events click
or timeout
, whether the user clicks the notification or it
times out. You listen to these events on the main notify object, not the
produces stream.
var notify = require('gulp-notify');
notify.on('click', function (options) {
console.log('I clicked something!', options);
});
notify.on('timeout', function (options) {
console.log('The notification timed out', options);
});
gulp.task("click", function () {
return gulp.src("some/glob/**")
.pipe(notify({ message: 'Click or wait', wait: true }));
});
Type: Reporter
Wraps options.notifier
to return a new notify-function only using
the passed in reporter.
Example:
var custom = notify.withReporter(function (options, callback) {
console.log("Title:", options.title);
console.log("Message:", options.message);
callback();
});
gulp.src("../test/fixtures/1.txt")
.pipe(custom("This is a message."));
This will be the same as
gulp.src("../test/fixtures/1.txt")
.pipe(notify({
message: "This is a message."
notifier: function (options, callback) {
console.log("Title:", options.title);
console.log("Message:", options.message);
callback();
}
}));
But much, much prettier.
The exact same API as using notify()
, but where a vinyl File
is passed, the error object is passed instead.
Example:
gulp.src("../test/fixtures/*")
.pipe(through(function () {
this.emit("error", new Error("Something happend: Error message!"))
}))
.on("error", notify.onError(function (error) {
return "Message to the notifier: " + error.message;
}));
Or simply:
gulp.src("../test/fixtures/*")
.pipe(through(function () {
this.emit("error", new Error("Something happend: Error message!"))
}))
.on("error", notify.onError("Error: <%= error.message %>"));
gulp.src("../test/fixtures/*")
.pipe(through(function () {
this.emit("error", new Error("Something happend: Error message!"))
}))
.on("error", notify.onError({
message: "Error: <%= error.message %>",
title: "Error running something"
}));
The onError()
end point does support lodash.template
.
onError()
will automatically end the stream for you. Making it easer for watching.
Type: Integer
Default: 2
Set if logger should be used or not. If log level is set to 0, no logging will be used. If no new log level is passed, the current log level is returned.
0
: No logging1
: Log on error2
: Log both on error and regular notification.
If logging is set to > 0
, the title and
message passed to gulp-notify
will be logged like so:
➜ gulp-notify git:(master) ✗ gulp --gulpfile examples/gulpfile.js one
[gulp] Using file /Users/example/gulp-notify/examples/gulpfile.js
[gulp] Working directory changed to /Users/example/repos/gulp-notify/examples
[gulp] Running 'one'...
[gulp] Finished 'one' in 4.08 ms
[gulp] gulp-notify: [Gulp notification] /Users/example/gulp-notify/test/fixtures/1.txt
If you are running on a system that handles notifications poorly or you simply
do not wish to use gulp-notify
but your project does? You can disable gulp-notify
by using enviroment variable DISABLE_NOTIFIER
.
export DISABLE_NOTIFIER=true;
This will disable all methods; notify()
, notify.onError
and notify.withReporter
.
To see all examples run from root:
$ gulp --gulpfile examples/gulpfile.js --tasks
[gulp] Using file /Users/example/gulp-notify/examples/gulpfile.js
[gulp] Working directory changed to /Users/example/gulp-notify/examples
[gulp] Tasks for /Users/example/gulp-notify/examples/gulpfile.js
[gulp] ├── multiple
[gulp] ├── one
[gulp] ├── message
[gulp] ├── customReporter
[gulp] ├── template
[gulp] ├── templateadv
[gulp] ├── function
[gulp] ├── onlast
[gulp] ├── advanceMac
[gulp] ├── error
[gulp] ├── forceGrowl
[gulp] └── customError
To run an example:
$ gulp --gulpfile examples/gulpfile.js multiple
[gulp] Using file /Users/example/gulp-notify/examples/gulpfile.js
[gulp] Working directory changed to /Users/example/gulp-notify/examples
[gulp] Running 'multiple'...
[gulp] Finished 'multiple' in 3.75 ms
gulp-notify
can easily be used as jshint reporter.
As jshint exposes the result on the vinyl file we can
use them in a function like so:
gulp.task('lint', function() {
gulp.src('/src/**/*.js')
.pipe(jshint())
// Use gulp-notify as jshint reporter
.pipe(notify(function (file) {
if (file.jshint.success) {
// Don't show something if success
return false;
}
var errors = file.jshint.results.map(function (data) {
if (data.error) {
return "(" + data.error.line + ':' + data.error.character + ') ' + data.error.reason;
}
}).join("\n");
return file.relative + " (" + file.jshint.results.length + " errors)\n" + errors;
}));
});
If you use a function for message in gulp-notify
, the message won't be shown.
This is true for both direct use of function and { message: function () {}}
.