Port already in use during yarn start

[jennifer-shehane]

I'm submitting a...

[ ] Bug report
[ ] Content update
[x] Process update (build, deployment, ... )

Type of bug / changes

When running yarn start, if the 3000 port is already in use, the docs continue to show a success message as if the docs are now running at port 3000 when in fact they aren't.

[jennifer-shehane]

Can we use a less common port than 3000? This is the same port that the services uses, for example. So if I"m running services, it's already in use and just opens the Dashboard.