If you have an & in your project's path you will run into this issue,
at least on Windows it seems like. The part in the path after the & is
interpreted as another command as per the error and everything breaks
from there.
Confirming that as soon as it's removed, npm start works fine.