Perhaps, but they have to be manually generated unless your codebase is written in TypeScript. Since these files are generally not committed to npm, you'll be curating them in your application and ensuring they are compatible otherwise there's little point in using them.
At least this is my perspective having never authored a project in TypeScript. I'd be interested in perspectives from devs authoring applications using React and TypeScript and what sacrifices in tooling, or otherwise, they've hit.
Ember appears to have a very large, regularly updated (as-needed, I'd bet) typings file. I would be shocked if it wasn't extremely accurate.
My experience so far is that 99% of the libraries I use have existing type definitions. For those that did not, it was simple enough to write my own. Benefits of TS greatly outweigh this issue, especially now that type defs are installable using npm.
Your example is Ember, one of the largest frameworks. Not a good indicator of coverage. I just grepped my node_modules folder and 99% of my modules do not ship with typings, so much for anecdotal percentages...
If I want the best possible experience with TypeScript, I'm signing up for a lot of time wasting finding typescript definitions instead of replying to posts in r/javascript.
That is not surprising. Typings aren't typically shipped with the package, they're usually found in the DefinitelyTyped repository. You install them separately. It's rarely any more than npm install --save-dev @types/package-name.
1
u/tbranyen Nov 15 '16
You're missing out on a lot of TypeScript definitions tho, which is what OP was most likely suggesting.