5 ms·

Here's to hoping that all my yarn caches will continue to carry me through this. Seriously, though. I'd love to get a look at their SLA and how they define "up

Here's to hoping that all my yarn caches will continue to carry me through this. Seriously, though. I'd love to get a look at their SLA and how they define "uptime" for their "org" and "enterprise" users. I don't think most teams are running out the door to throw their money at npm, and it's this type of instability that creates mistrust amongst developers.

spondyl 8y ago
Yarn seems to be unaffected with this issue so I imagine you'll be fine. There's been a few users (including myself) who simply swapped out npm for yarn and have had the issue resolved. It doesn't really address the root cause but in this case, it's presumably some bit of logic in the actual npm client itself rather than the registry.
- olingern 8y ago
  Last time I checked the yarnpkg registry is still a proxy to npm, unless they've started hosting. I haven't checked in some time.
  - fold_left 8y ago
    You're right
  - lnanek2 8y ago
    yarn is basically an npm wrapper that add caching, so even so, it's good for avoiding intermittent errors