Tech stack unification

[impact-maker]

The upcoming revision of the Chromestatus API will incorporate OpenAPI specifications, enhancing its structure and accessibility. Concurrently, a transition from JavaScript to TypeScript is planned, aimed at improving the health of the codebase

[impact-maker]

I've been dedicating significant effort to the Chromestatus project, from setting up the development environment to tackling initial bugs. I'm eager to gain a clearer understanding of the objectives, specifically the features or enhancements targeted for this release cycle. If there are any resources or documentation available, sharing links would be highly beneficial.

Additionally, I'm curious about whether there's an ongoing or planned shift from JavaScript to TypeScript for the project. If such a transition isn't already in the pipeline, I'm considering proposing several issues or pull requests to initiate this change

For further discussion and guidance, I've tried to reach out to @jrobbins and @DanielRyanSmith via email at mdeep9771@gmail.com. Eagerly awaiting your guidance and perspectives on these issues