Package Exports
- gulp-notify
- gulp-notify/lib/extra_api
- gulp-notify/lib/notify
- gulp-notify/lib/report
- gulp-notify/lib/withReporter
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (gulp-notify) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
gulp-notify

notification plugin for gulp
Information
| Package | gulp-notify |
|---|---|
| Description | Send messages to Mac Notification Center or Linux notifications (using notify-send) using the node-notifier module or Growl if not any of them. Can also specify custom notifier. |
| Node Version | >= 0.8 |
| Package Version | 1.2.4 |
Note: Without overriding the notifier, Mac OS X >= 10.8 or as of v0.3.2, Linux with notify-send installed is required for this to run.
After version 1.1.0 this now supports Growl natively.
Usage
First, install gulp-notify as a development dependency:
npm install --save-dev gulp-notifyThen, 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 og the API section for various inputs.
Notes/tip
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!"))
}));API
notify(String)
A message to notify per data on stream. The string can be a lodash template as it is passed through gulp-util.template.
notify(Function)
Type: function(VinylFile)
The result of the function is used as message. Vinyl File from gulp stream passed in as argument.
The returned string 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.
notify(options)
Options are passed onto the reporter, so on Windows, you can define Growl host and so on. See node-notifier for more information
options.onLast
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.
options.message
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 %>.
as function
Type: Function(vinylFile)
See notify(Function).
options.title
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 %>.
as function
Type: Function(vinylFile)
See notify(Function).
options.templateOptions
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()
}
}))options.notifier
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.
notify.withReporter(Function)
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.
notify.onError()
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.
notify.logLevel(level)
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.txtExamples
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] ├── error
[gulp] └── customErrorTo 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 msAs jshint reporter
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 () {}}.
Changelog
v1.2.1
- The entire options-object is passed to the notifier, allowing pass additional information to notifiers.
- Adds support for showing errors returned from the notifiers and showing these errors in the console.
v1.1.0
- Bumps dependency for
node-notifier. Now supports Growl on Windows!
v1.0.0-beta
- Major rewrites and restructure in code
- Lock down on API, changes
setLogLeveltologLevel - Exposes logLevel and logger on the withReporter object.
v0.6.2
- Adds another logging level: 0 - none, 1 - error, 2 - all.
v0.6.1
- Added
.onErrormethod on object created bywithReporter - Added colored logging on success / error
v0.5.0
- Added API end point
notify.withReporter(Reporter)as syntactic suger for custom reporter - Updated dependency for node-notfier - now checking if
notify-sendis installed on the Linux box