Why is PORT constantly busy?

Question

Express.js

Hello guys, I have such a problem, I switched from Webstorma to VS code, purely for the sake of interest, but after I switched in my terminal (bash.exe) it gives an error that port 3000 (client) and 3003 (server) are busy, but at the same time, everything works just if something crashes, the terminal does not show because somewhere in the background some other terminal is working. I don’t know if I could explain the essence of the problem to you or not ((I will be glad if you explain what the garbage is.
By the way, on win10 I even killed these ports several times through the command line (cmd) anyway, when npm start the terminal shows that these ports are busy.
Here is an example from the server
events.js:160 thrower; // Unhandled 'error' event
[nodemon] app crashed - waiting for file changes before starting...
but the server is still running. In short, like this.

Answer 1

To minimize problems:
I can’t tell you about VS Code, alas :( WebStorm itself kills the processes it creates, so there is no such problem.