Visual Studio Code 1.7 overloaded npmjs.org, release reverted

Post by Fifer82 » Thu, Nov 03, 2016, 4:03 PM UTC

seldo wrote: post #13

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 feature…

Post by [deleted] » Thu, Nov 03, 2016, 4:08 PM UTC

kozhevnikov wrote: post #48

seldo wrote: post #22

Earlier quoted context omitted.

A VSCode person can (and probably will) answer in more detail, but at heart it's simple: if you want to add type-checking goodness to a library that isn't itself written in TypeScript, you can create a thing called a declaration file: https://github.com/DefinitelyTyped/DefinitelyTyped Microsoft publishes a list of known good declaration files for popular npm packages to npm, under the scope @types: https://www.npmjs.…

Can they publish a package that contains a list of all their other packages under @types?

Post by JohnHaugeland » Thu, Nov 03, 2016, 4:18 PM UTC

seldo wrote: post #22

Arnavion wrote: post #14

Earlier quoted context omitted.

Can you elaborate on what the issue is and how you want it to be fixed? Is it just something like rate-limiting requests or something more fundamental? Edit: Answered at https://news.ycombinator.com/item?id=12861118

A VSCode person can (and probably will) answer in more detail, but at heart it's simple: if you want to add type-checking goodness to a library that isn't itself written in TypeScript, you can create a thing called a declaration file: https://github.com/DefinitelyTyped/DefinitelyTyped Microsoft publishes a list of known good declaration files for popular npm packages to npm, under the scope @types: https://www.npmjs.…

Post by mirhagk » Thu, Nov 03, 2016, 5:01 PM UTC

onlydnaq wrote: post #47

seldo wrote: post #22

Earlier quoted context omitted.

A VSCode person can (and probably will) answer in more detail, but at heart it's simple: if you want to add type-checking goodness to a library that isn't itself written in TypeScript, you can create a thing called a declaration file: https://github.com/DefinitelyTyped/DefinitelyTyped Microsoft publishes a list of known good declaration files for popular npm packages to npm, under the scope @types: https://www.npmjs.…

> At the moment there are few enough that they could fetch a list of all of them and cache it (the public registry lacks a documented API for doing that right now, but we can certainly provide one) Might I suggest having a bloom filter containing all the existing type declaration (which would be quite small) and only querying the registry if the bloom filter reports the type declaration as a positive. Since the filte…

Post by Yugnik » Thu, Nov 03, 2016, 5:41 PM UTC

mirhagk wrote: post #87

onlydnaq wrote: post #47

Earlier quoted context omitted.

> At the moment there are few enough that they could fetch a list of all of them and cache it (the public registry lacks a documented API for doing that right now, but we can certainly provide one) Might I suggest having a bloom filter containing all the existing type declaration (which would be quite small) and only querying the registry if the bloom filter reports the type declaration as a positive. Since the filte…

Is there an efficient diff algorithm for bloom filters?