Hi Jeff,

npm cache clean didn’t get rid of the error. I am using Windows 10, not sure if that makes a difference.