Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Livereload keep listening to the port after gulp exits for errors #104

Open
p0o opened this issue Oct 26, 2015 · 6 comments
Open

Livereload keep listening to the port after gulp exits for errors #104

p0o opened this issue Oct 26, 2015 · 6 comments

Comments

@p0o
Copy link

p0o commented Oct 26, 2015

Every time there is an error and gulp exit, I should type "netstat -peanut | grep 8080" and find the listening process and kill it, otherwise I'm unable to start my gulp tasks again.

Is there any workaround available for this issue?

@baptistedonaux
Copy link

+1

@p0o
Copy link
Author

p0o commented Nov 10, 2015

I managed to solve the problem by using plumber for error handling in the first stream of my livereload task. It will handle to exit the process properly.

var plumber = require('gulp-plumber');
....
.pipe(plumber())
.
.
.
.pipe(livereload());

@baptistedonaux
Copy link

thanks @p0o

@brandonburkett
Copy link

I am running into this as well, it seems livereload is keeping our gulp tasks open in webstorm.

@leo
Copy link

leo commented Feb 17, 2016

Hey, @p0o ! Just wanted to let you know that I've created a standalone fork of this repo, since it doesn't seem to be maintained anymore. You can find it here.

So I might be a good idea to re-open this issue there.

@p0o
Copy link
Author

p0o commented Feb 19, 2016

@leo Thank you for the hint. We dropped Livereload alongside with the whole gulp task runners from our project and replaced them with NPM scripts and Webpack. You may open it yourself since I'm not an active user anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants