2 ms·
If the library has it's own .d.ts file in the repo, it will just work. Otherwise, the @types packages on npm are the way to go. Please note that most of the @
by the_duke 10y ago
If the library has it's own .d.ts file in the repo, it will just work.
Otherwise, the @types packages on npm are the way to go.
Please note that most of the @types/XXX packages are just automatically extracted from the DefinitelyTyped repo. Big packages with lot's of updates can use their own repo.
But this is a huge, huge usability win.
No more haggling with additional tools to get your typings.
- tga 10y agoFrom a usability point of view is it really such a huge huge win that instead of using `typings install foo` you can now use `npm install @types/foo`? I can see it's better (not sure why a single repository(!) was ever considered a good idea), but in the end both methods work if all you need is to obtain the latest version of a .d.ts file.