404 if another process is started on the same port

I followed the simple example with a db.json and ran json-server --watch db.json. Everything seemed to work fine but I ran into 404s when trying to access any route (ie: http://localhost:3000).

Turns out I had another process running on port 3000.

The console did not throw any error though.

[jacobwardio]

If something else is running on a specific port used by a cli app, most others (that I’ve come across) either:

• Error out and tell you that something else is blocking the port it wishes to use.
• Increment the port number and try again (repeat until success).

Either of these seem like reasonable approaches, with the second being my preference.

[jessycormier]

@jacobwarduk Just trying to provide a solution as I didn’t know your environment/setup 😃