Why don't you add TypeScript or Flow type definitions to your modules?

[SamVerschueren]

Could you please answer this once and for all so I can link the answer to people who are doing a PR and trying to add it. I know your statement but people want to hear it from you if I answer them "add it to DefinitelyTyped".

[jfmengels]

Same thing about Flow types :)

[sindresorhus]

I use neither TypeScript nor Flow in my small modules as I don't yet see enough value. If I were to accept type definitions, I would have to maintain them. Which I would do badly. I would say bad definitions are worse than none. DefinitelyTyped and flow-typed are good solutions to this problem. Submit the type definitions there instead.

That being said, I do accept type definitions in larger projects when it makes and someone offers to maintain them. For example, we have both TypeScript and Flow type definitions in AVA. Also, a while back, I adopted Flow in the Pageres codebase.

[sindresorhus]

I initially didn't want TypeScript definitions in my packages as I didn't use TS so I wouldn't be able to maintain the definitions and I felt TS was too immature. These days I'm using TS more and with TS 3, its become a lot more mature, so I have decided to start accepting TypeScript type definitions for my packages.

Please follow this guide when submitting a type definition:
https://github.com/sindresorhus/typescript-definition-style-guide

I am, however, not accepting Flow type definitions. I just don't have the time or interest in maintaining type definitions for something I don't use. Submit it to flow-typed instead.

[zikaari]

Glad to have you on board 😌