Dylan

> I had similar problem - what helped was running `npm start -- --reset-cache` command. If you use yarn, write yarn instead of npm

v5.2.0 causes this problem but v5.2.1 does not.