CLI does not throw an error when starting app on a port that is unavailable
Closed this issue · 1 comments
nkshah2 commented
When starting the app it does not quit if the port is already taken, instead it prints out a normal info message
One way to fix this problem is to use a unique port number other than 3000 and 3001
nkshah2 commented
Since the CLI does not auto start the application, this is no longer relevant