gulp-watch & gulp-nodemon

[ghost]

I'm using gulp-watch package that starts also gulp-nodemon, like so:

gulp.task('gulp-nodemon', function() {
  nodemon({
    script: 'test/fixtures',
    watch: 'test/fixtures',
    ext: 'js json'
  });
});

gulp.task('watch', ['gulp-nodemon'], function() {
  gulp.start('browser-sync');
  watch('app/**/*', function() {
    browserSync.reload();
  });

However, when I quit the gulp watch command with Ctrl + c, then nodemon process is still running. Is there a way how to cleanly exit the process?

[scottseeker]

I have the same issue.

[eliot-akira]

Same here. After quitting gulp with Ctrl + c, the process continues to run - and when I enter any key on the bash command line, the process finally ends with an error:

events.js:141
      throw er; // Unhandled 'error' event
      ^
Error: read EIO
  at exports._errnoException (util.js:837:11)
  at TTY.onread (net.js:544:26)

I've tried different methods to prevent this, but so far no success. The only workable way I found was to run nodemon and gulp separately. I'll be checking back on this ticket to see if anyone finds a better solution.

---

Edit: In my case, the issue was not with gulp-nodemon but a mistake in the setup. I had a watch task manually reloading browser-sync, when it was already watching the same files.

[mshwery]

same

[eliot-akira]

For me, the following finally solved this issue:

var monitor = nodemon(options);

process.once('SIGINT', function() {
  monitor.once('exit', function() {
    process.exit();
  });
});

Without this handler, the process doesn't exit on Ctrl+C and then throws an error on TTY.onread. With it, it exits clean. I have several watch tasks including nodemon and browser-sync, so your mileage may vary.

[mshwery]

@eliot-akira what is process for you in this closure? nvm

[theverything]

Thank you for this thread I've been having this issue for the last couple weeks and couldn't figure out why.

I used a modified version of @eliot-akira fix. Which seems to have removed the error.

gulp.task('server', function () {
  nodemon({
    script: './server.js',
  })
  .once('exit', function () {
    console.log('Exiting the process');
    process.exit();
  });
});

[PeterPanen]

@theverything
It seems here that the nodemon exit event also gets triggered when nodemon restarts, due to file changes.

Listening for SIGINT like @eliot-akira mentions seems to work better for now at least.

[glortho]

@eliot-akira thank you!

[bavellone]

@theverything Just what I was looking for. Thanks!

[ColemanGariety]

I think this is a duplicate of #33.

[jwickens]

The following works pretty well for me:

    nodemon.on('start', () => {
        debug('nodemon has started app');
    }).on('quit', () => {
        debug('nodedmon has quit');
        process.exit();
    }).on('restart', function(files) {
        debug('App restarted due to: ', files);
    });