As one of the folks on the front-lines helping patch this, I certainly have no hard feelings; and I'm excited to be able to support this feature properly
... also ... not going to lie, this was the first time we've gotten to test several of the checks and balances we have in the npm registry which I was jazzed about :)
If I were on the Azure team I'd be offering tons of free credit to npmjs.org to get them to use Azure. Azure coming to the rescue would be the perfect ending to this story for Microsoft.
Shouldn't all these requests be cached by a CDN? What exactly is overloading?
It is a real foreign feeling being exposed to such an actively and well run project. Every time I see a new release on HN I get a little "wow, that time of the month again." Even this rollback was indicative of how fast they move.
Which is more possible? A bug or they just underestimated the volume of traffic that could be caused by ATA in real life?
Would yarn help here? (since FB have their own CDN and registry for it?)
I wonder if any warning was given to npm that they would be getting this potentially huge new source of traffic. It doesn't seem to be mentioned anywhere.
This is a really cool feature! Is there a similar extension for Atom / Sublime?
Damn it, M$! Keep your shit closed. Not everybody wants you messing around.
oops
But they told us that pulling in 1.6 GB for "Hello World" is normal and no big deal.
I'd love to use VSCode but can't until they or someone else rolls out a dockblockr extension that works for php as I'm mostly tied to Laravel right now, and my company requires docblocks and they are not fun to write by hand.
They are probably trolling for a debate about NPM ... I can smell politics.
> The feature was so great that we started to overload the npmjs.org service.
I'm not sure I would call my feature "great" if it could have brought down npm.
I'd just like to say on behalf of npm that Microsoft's handling of this incident was A+. As soon as we alerted them to the issue they were all hands on deck and did a rollback.
We've been really pleased that Microsoft chose to put their @types packages into the npm registry rather than a separate, closed system, and in general happy with Microsoft's support of node and npm. We're confident we can make the new features of VSCode work, we just need to work with Microsoft to tweak the implementation a little.
This was an honest mistake on their part, and we caught it in time that there was very little impact visible to any npm users.
Fun fact: at its peak, VSCode users around the world were sending roughly as many requests to the registry as the entire nation of India.