BrowserSync Notify

[NgYueHong]

I hope that the notify setting can be upgraded to be able to disable default message but still can display specially requested to notify message.

I personally found that every time when page reload, it shows "Connected to BrowserSync" is very annoying, but I want to be able to display custom message from gulp when needed. Currently when the notify is disabled, the custom message will also not displayed as well.

Hope there will be an upgrade for this soon. Thank you.

[shakyShane]

@NgYueHong - the convention in other areas of the api is to have an override option.

I propose

var bs1  = require("browser-sync").create();

bs1.init({
    server: "./app",
    notify: false
});

// later in your code...
bs1.notify("Compiling templates, please wait...", {override: true});

[shakyShane]

[email protected] will work as expected.

var bs1  = require("browser-sync").create();

bs1.init({
    server: "./app",
    notify: false
});

bs1.watch('./app/*.css').on('change', function (file) {
    bs1.notify(file + ' changed');
});

[NgYueHong]

Great! Thanks a lot for your great work.

[olets]

@shakyShane I'm running some compilation, and then trigger browserSynch.reload(). Trying to set up a (file + 'changed')-type notification, but can't figure out where to build it in. The basic idea is

var browserSync = require('browser-sync');
gulp.task('browser-sync', function() {
    browserSync.init({
        server: {
            baseDir: 'compiled/'
        }
    })
});
gulp.task('browser-sync:reload', function () {
    browserSync.reload();  
});
// more tasks that call browser-sync:reload

How would this work?

[AlexGalays]

I can't see any custom notifications if notify = false with @2.15.0

[cmalven]

I'm having the same issue in 2.18.7. bs.notify() doesn't show anything if notify: false is in the config.

[shakyShane]

Fixed - will be released at some point today

[hlolli]

I'm on 2.23.6 if I do notify: false, I can't in any way send notifications, with or without override: true.

[mathisonian]

I'm seeing the same issue as @hlolli in 2.26.3.