It’s a bit late, but if you still haven’t resolved the issue, try running npm start -- --reset-cache instead of npm start --reset-cache. That worked for me.