Add type definitions badge

[paulmelnikow]

Hi @sindresorhus! I added this badge to Shields at your suggestion badges/shields#1252, and though I'd see if you'd like to include it here!

[sindresorhus]

Is there any way to get the badge without the version numbers? The badge is very long and I don't see much value in having those version numbers.

[paulmelnikow]

It is really long.

The reason I had included the version numbers was to help developers distinguish between well maintained libraries, whose defs are being kept up to date, and libraries which aren't. It seems like the version number is useful for that. That said, I'm relatively new to TypeScript and Flow so I appreciate your perspective on this!

1. 
2. 
3. 
4. 
5. 

Further thoughts?

[sindresorhus]

The reason I had included the version numbers was to help developers distinguish between well maintained libraries, whose defs are being kept up to date, and libraries which aren't. It seems like the version number is useful for that.

What if my library is mature and stable and doesn't need updates? Many packages don't even have TS or Flow as development dependencies.

---

I would go for number 2.

[paulmelnikow]

I see. Thanks. 👍

Could I ask a couple other questions?

For packages that don’t declare the dependencies, is there a better way to infer their type support?

Is it possible that a future breaking change to the language would require definitions to be updated, even if the library is mature?

[sindresorhus]

For packages that don’t declare the dependencies, is there a better way to infer their type support?

For TS, you could look for a index.d.ts file in root or a types field in package.json.

For Flow, you could look for a index.js.flow file in root or a flow-typed directory in root.

Is it possible that a future breaking change to the language would require definitions to be updated, even if the library is mature?

Yes, but I don't think a version is a good enough indicator of that. TS might break a library in a minor release or never. It really depends on what features you use and how. For simple node modules, it's unlikely new versions will break much.

[paulmelnikow]

Great. Thanks so much for the feedback. Give me a few days and I will make some updates to the badge.

[sindresorhus]

@paulmelnikow Can this be finished now?

[Qix-]

Late to the game but 2 was the choice I would have made as well.

Just for some validation 💃

[Qix-]

Resolved the conflicts (will need a squash merge). Only issue I see, which is super nit-picky, is a wrap of a single badge:

[sindresorhus]

We can drop the Awesome badge.

[Qix-]

SGTM, thanks @sindresorhus and @paulmelnikow!

[paulmelnikow]

Ah yep! Thanks for merging this!