React, Flux, GraphQL, Hack, HHVM...? All of this and more!
- Visual Studio Code 1.7 release announcement
This indicates that the feature is useful, causes a lot of traffic and verifies that TypeScript is not a niche technology by any means. The developer team at Microsoft also did the right thing in reverting the version with this feature. Very responsible action from a mature software company.
According to the NPM staff working together with the Visual Studio Code team the functionality in the editor ended up creating a lot of requests that resulted in 404s that we not cached:
CDNs don't usually cache 404s. VSCode was looking for @types packages for any and every npm package its users were using. Packages that had a type description caused no issue, but most packages don't, so we had a > 1000% spike in 404s. Our workaround before MS did the rollback was to cache 404s for @types packages specifically, and it was effective enough that the registry never really went down.
- Laurie Voss of NPM
...and would've made a great headline in the early 2000's. But it's beyond the point. So the automatic Type Definition download feature can for sure be optimised to cause less traffic to NPM in the future for the feature to return. And the team is taking this with humor:
Putting "Led the design and implementation of an infrastructure to DDoS NPM" top and center in my self-assessment this year— Ryan Cavanaugh (@SeaRyanC) November 3, 2016
In neither cases there was no malicious intent, but in case someone wanted to interfere with a large chunk of the global developer audience could be made unproductive by attacking a few key services like Github, NPM and Slack. All commercial entities that Open Source development is very dependent on.Tweet