Comment by nwalters512

The npm folks have officially acknowledged an incident now: https://status.npmjs.org/incidents/hdtkrsqp134s