Port in use error

[mrberggg]

I'm getting an error intermittently when running npm run start: Error: listen EADDRINUSE :::3002. It appears it's an error caused by that port being currently in use. If I rerun the command it usually works. Not a biggie, just an annoyance. If I knew what was going on I'd be happy to submit a PR. Thanks for your work, love this!

[coryhouse]

Yep, this happens in two scenarios:

1. When you already have the starter kit running on another command line.
2. The default port is conflicting with some other process on your machine.

You can specify a different port to see if that helps. Add the following to the browserSync call in /tools/server.js:

browserSync({
port: 9080,
ui: {
port: 9081
},

I'm considering adding this to the kit so the configuration is easily available.

[mrberggg]

I can't find any other processes running on that port which is what was confusing me. But I'll try changing the port, see if that fixes it. Thanks!

Oh and do you take feature requests? It'd be great to have connect-history-api-fallback or some HTML History config (i.e. support for SPA routing).

[nickytonline]

@mrberggg for routing, see issue #10.

[mrberggg]

Yeah, I saw that. Including it in the build step doesn't seem opinionated though (doesn't add any weight to final bundle) and it would save a lot of headache in setup. Anyhow, thanks for your work