Christopher Cox

In case this helps anyone, I had this issue as well. It turned out to be a problem with my local npm cache. Try this: ``` npm cache clean --force...

Thanks for fixing this @ryan-roemer! I didn't realize it was fixed until I read through the releases, do you mind closing the issue?