For those not following the issue, I wanted to re-post the following possible resolution. We think this may have been caused by a temporary problem with the npm servers last week and need confirmation. From @kevinsawicki’s comment on the issue:
Can people try removing the following directories, reinstalling the packages that are showing errors, and see if they still see this issue?
These are just cache directories used to store modules and libraries, not actual packages.
@nathansobo pointed out there was a recent npm server issue causing empty tarballs.
Empty tarballs responses
Resolved - Cache invalidation is complete.
Sep 16, 16:29 UTC
Monitoring - Cache invalidation is ongoing and should be complete within 15 minutes.
Sep 16, 15:55 UTC
Identified - A bug in code we rolled out to our canary server at 10:52 UTC today, and which our automated checks haven’t caught caused us to return empty tarball responses to some of our users. We rolled the deployment back at 14:29 UTC and are working on invalidating caches affected by this outage.
Sep 16, 15:25 UTC