Convert to TypeScript

[mpeyper]

Describe the feature you'd like:

Title says it all. I feel like TypeScript has reached a level of adoption where we shouldn't be scared of losing contributors by using it instead of JavaScript.

I believe other @testing-library packages are considering or currently being converted, if they aren't already TS.

Suggested implementation:

We currently have type definitions in DefinitelyTyped which can be used as the basis of the types.

I think we can aim to have a straight cut over to a new codebase rather than a progressive migration as there are not that many files to consider.

I think we should look at using TSDX for the tooling unless anyone has other ideas or suggestions in this space.

Describe alternatives you've considered:

N/A

Teachability, Documentation, Adoption, Migration Strategy:

This package should also become the source of truth for the type definitions and the DefinitelyTyped version should be deprecated. I'm not sure what the process if to do that if there is one.

Other than that I don't think there are any particular considerations to be made for this.

[joshuaellis]

The compiler won't recommend looking for @types/* library anymore because we'll have bundled types. So I imagine they would be able to put a depreciated flag on the package?

Is there a reason you think we should tsdx? Looking at the repo, it's pretty immature and there's a few outstanding issues. I think we could probably just use our own configuration. Proabably easier to maintain overall.

[nickserv]

I think we should look at using TSDX for the tooling unless anyone has other ideas or suggestions in this space.

kcd-scripts now supports TypeScript and it's already the de facto standard tool for this organization.

This package should also become the source of truth for the type definitions and the DefinitelyTyped version should be deprecated. I'm not sure what the process if to do that if there is one.

There's a list of removed packages that you can submit a pull request to.

[mpeyper]

Is there a reason you think we should tsdx?

Only that I have seen folks on Twitter mention how nice it was to use.

I'm also happy with kcd-scripts if that is the preferred approach.

[marcosvega91]

If you want I can migrate the actual codebase to kcd-scripts.

[nickserv]

In that case it's probably easier to do #499 with yo kcd-oss first. We'll have better CI for this PR and TS tooling setup will be simpler.

[marcosvega91]

Yes, sure

[tigerabrodi]

@marcosvega91 @mpeyper I'd love to help when it comes to migrating to TypeScript 💕

[mpeyper]

@tigerabrodi

You can start building off the changes in #502 which I'll merge as soon as I'm on my laptop next (I need to update some repo settings first)

[tigerabrodi]

@mpeyper Do you mean building in the same PR as @marcosvega91? Then he would have to give me permission as a collaborator to be able to push changes there, or am I missing something?

I could start building once that PR is merged 🙌 🥰

Thanks for the opportunity also 🙏 💕

[mpeyper]

No, I mean pull down his PR branch, branch from there, and start committing onto it. Then rebase to master once I've merged it (within 24 hours).