Glenn R. Martin

@KITSDominicWhite so the official line would be "Gulp4 has not been released in a final form", but I hate it when people respond like that... so I'll do the best...

@KITSDominicWhite any luck?

@KITSDominicWhite No worries! If i can assist or if you get it working, please let me know.

I don't have an answer to this off the top... i'm willing to do some digging though... But i need to know: 1. Are these PHP errors (like Syntax parsing)...

@vieko I am presently in the process of reworking portions of this, including its dependence on `lsof`. The current status of where i am in this is available here: https://github.com/micahblu/gulp-connect-php/pull/41...

1.0.0 is now in the primary master branch of the original repository. See: http://github.com/micahblu/gulp-connect-php.

This ticket will close on or near 17 May 2017 unless updated.

So, Gulp 3 uses [orchestrator](https://www.npmjs.com/package/orchestrator). Presently our library doesn't implement any binding to Gulp's events. That would be why its not 'automatically' stopping, there is a [`closeServer` call](https://github.com/micahblu/gulp-connect-php/blob/68ce3a01c000a2167a32ffc4e1006e1bf9cde17a/index.js#L104). For now...

@micahblu, I can add this but I'd like to make it so it can be opted out from via a configure parameter... any issues with that conceptually?

Actually, it has me curious. Ill play with it and see if i can figure out why. ... im not sure id expect a user to realize that and if...