Policy on typing

[gfellerph]

What's the policy going to be concerning types? Looking at the popularity of TypeScript in the State of JS surveys JavaScript/TypeScript balance, I presume this library should export typings in some way. What is expected of contributors when authoring components?

• Should components be contributed in typescript only?
• Should contributors be able to write JS and provide types through other means like definitely typed?
• Should there be typings provided for multiple type systems like flow or JS Doc?

[gregwhitworth]

This is a great topic as aligned DX is definately something we've raised. Typescript will help a lot in a system like this so I personally can see this being our preferred approach for a component that lands within the component library. I don't think that it would block someone from bringing a solution but I definately think it will help us in build process and help people land their components.

[lukewarlow]

If we use custom elements manifest there's a lot of tooling that can utilise that, and some of those integrate well with TypeScript I believe (and also produce useful files for IDE autocomplete).

[lukewarlow]

https://github.com/break-stuff/cem-tools/tree/main/packages/jet-brains-integration#readme - this for example will generate IDE typing for JetBrains, a similar tool exists for vscode I believe (that repo seems to have lots of tools to me)