-
Notifications
You must be signed in to change notification settings - Fork 67
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
Comments
+1 |
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()); |
thanks @p0o |
I am running into this as well, it seems livereload is keeping our gulp tasks open in webstorm. |
@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. |
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?
The text was updated successfully, but these errors were encountered: