BrowserSync couldn’t exit a Gulp task if there’s a server configured

Details

I’m trying to run a local server and take a screenshot of a page using pageres, but BrowserSync couldn’t exit() a Gulp task if there’s a server configured.

Steps to reproduce

1. npm install gulp pageres browser-sync
2. touch gulpfile.js with contents below
3. gulp one and gulp two, compare results

const gulp = require('gulp');
const pageres = require('pageres');
const sync = require('browser-sync').create();

gulp.task('server-one', () => {
    sync.init();
});

gulp.task('server-two', () => {
    sync.init({
        server: {
            baseDir: '.'
        }
    });
});

gulp.task('pageres', () => {
    return new pageres()
        .src('localhost:3000', ['1024x640'], {
            crop: true,
            scale: 2,
            filename: 'localhost'
        })
        .dest('.')
        .run()
        .then(() => sync.exit());
});

gulp.task('one', ['server-one', 'pageres']);
gulp.task('two', ['server-two', 'pageres']);

The only difference between one and two is

server: {
    baseDir: '.'
}

But in two case BS doesn’t exit task.

Versions

• Browsersync 2.11.2
• Node v5.10.0
• Npm v3.8.3

Affected platforms

• OS X

Use-case

• Gulp

[shakyShane]

This is actually an issue with the socket.io server. Once a browser is connected even a single time, the tear-down logic within socket.io or engine.io is not running as expected. You can prove the by running Browsersync with open:false and then calling bs.exit() after a few seconds. On Sat, 29 Oct 2016 at 11:50, tcme [e-mail] wrote:

do you use bs.watch somewhere? In my case the process does not exit if I use bs.watch see #1222 https://github.com/BrowserSync/browser-sync/issues/1222

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/BrowserSync/browser-sync/issues/1052#issuecomment-257084753, or mute the thread https://github.com/notifications/unsubscribe-auth/ABkUAo1Bwjd5Bwhmm51C86vPFnG41-p_ks5q4yT8gaJpZM4ICm4o .

[IgnusG]

I’m running into the same problem. I presume it was never fixed?