Using connect with watch to serve results in EADDRINUSE about grunt-contrib-connect

[sindresorhus]

EADDRINUSE means the port used (8000) is already in use by another process. I just committed a better error message for that.

It most likely has to do with you also using the 8000 port for the reload task. Change either of them and it should work.

[mattd]

Nope, unfortunately not. Sorry - should have noted that earlier. Removing the reload tasks and all of the applicable mentions from my Gruntfile makes no difference. I still get the same port error.

[sindresorhus]

@mattd Can you try using a different port for the server task? Might be something else then using that port.

[mattd]

Choosing from a bunch of totally random ports (6474, 2567, 8945) doesn't make any difference.

[sindresorhus]

Hmm, ok. Does the same thing happen with grunt connect? Which grunt version are you using?

[mattd]

If I do grunt connect watch, the same thing happens. If I do just grunt connect, it (correctly) immediately closes because it's not watching.

For versions, my package.json looks like this: https://gist.github.com/3990775

[mattd]

So after some deeper investigation, it looks like this is actually a bug in grunt-contrib-watch and not grunt-contrib-connect. I've created a new issue there. gruntjs/grunt-contrib-watch#12