Visual Studio Code 1.7 overloaded npmjs.org, release reverted
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.