Npm start says something is running on EVERY port I try but serve -s build works fine on any port I use...

[bostonareahuman]

Describe the bug

Npm start says something is running on EVERY port I try but serve -s build works fine on any port I use...

Did you try recovering your dependencies?

9.2.0

Which terms did you search for in User Guide?

(Write your answer here if relevant.)

Environment

(paste the output of the command here.)

Steps to reproduce

(Write your steps here:)

1. npm start

Expected behavior

see the server up and running

(Write what you thought would happen.)

Actual behavior

✔ Something is already running on port 3000.

Would you like to run the app on another port instead? … no

Reproducible demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

[mathiasbosman]

Assuming "start" uses npm run react-scripts start this works fine on a clean project for me.

[ice1080]

I'm also running into this issue. When I try something like

PORT=8087 npm run start

I still get Something is already running on port 8087. I changed nothing about my project and it was working 4 days ago. Never ran into this issue before. From other sources online, it seems that something about the code is trying to start the app after it's already running, or double start the app or something.