This isn't an issue related to any of type definitions rather to improve this repo and make it more consistent and more user friendly for old/new contributors.

Repo updates

• we really need consistent formatting ( incorporating prettier is viable choice )
• provide npm scripts for executing prettier + linter fixes so user doesn't have to do it on it's own manually
• provide githooks ( pre-commit 👉 formatting and lint fixes applied automatically )
• provide automated changelog generation with every release ( this is a must have as breaking changes can occur even on fix or feat semver bump, and it's not very user friendly to go through commit log what changed in some particular package )
• be able to run whole test suite from local machine and not wait for CI
• provide some codemods/scripts for updating all packages dependant on some other core package
  • for example: I update react types with some breaking change from type safety perspective ( bump minimum TS version ) or tweak API type coverage, now I have to manually go through 5k+ packages and update all of them ( which is super annoying especially if you have to resolve merge conflicts )
• enforcing consistent commit messages

Docs updates

• consistent pull request/issues naming
  • as can be observed a most used pattern is [package-name]: issue/pr description
• make clear what a breaking change means
  
• IMHO it should be a breaking change only if the library bumps semver as breaking ( if we change some types to be better and expose new type-errors, it should not be bumped == same methodology as TypeScript team is doing )

Summary

If we agree at least at some of these points, I can start work on this immediately 💪

cc @sandersn @Andy-MS @mhegazy @DanielRosenwasser