Thursday, 13 February, 2020 UTC
Summary
Feb 13, 03:38 UTC
Resolved - Thanks for your patience. The issues we identified today have been resolved.
Resolved - Thanks for your patience. The issues we identified today have been resolved.
Feb 13, 00:10 UTC
Update - We are continuing to investigate this issue.
Update - We are continuing to investigate this issue.
Feb 13, 00:09 UTC
Update - We're continuing to look into this issue. For most users, we're at 100% functionality. Some, unfortunately, will see 404s.
We are seeing a pattern with packages that have the word "error" in their name.
Just a reminder that we recommend using `npm ci` and not `npm i` in your automated CI/CD pipelines.
And, please, help me in thanking our engineering staff. They have delivered fast teamwork from around the world in response to your reports. We really appreciate the community feedback.
Update - We're continuing to look into this issue. For most users, we're at 100% functionality. Some, unfortunately, will see 404s.
We are seeing a pattern with packages that have the word "error" in their name.
Just a reminder that we recommend using `npm ci` and not `npm i` in your automated CI/CD pipelines.
And, please, help me in thanking our engineering staff. They have delivered fast teamwork from around the world in response to your reports. We really appreciate the community feedback.
Feb 12, 20:36 UTC
Investigating - We are investigating a separate issue where some users are noticing 404's, and we're noticing different results depending on location.
It seems like this occurs on packages with `error` in their name, and varies by location.
Thank you for your patience while we investigate further.
Investigating - We are investigating a separate issue where some users are noticing 404's, and we're noticing different results depending on location.
It seems like this occurs on packages with `error` in their name, and varies by location.
Thank you for your patience while we investigate further.