Final Friday, the Ember venture merged RFC #0724: Official TypeScript Assist, committing to make TypeScript an officially-supported language for Ember.js. To make {that a} actuality, we additionally must have a workforce devoted to sustaining Ember’s varieties and its TypeScript compiler integrations.
Fortunately, we have already got a gaggle of people that do this! For the final 5 years, Ember has had community-driven TypeScript help, led by the previous and current members of the Typed Ember workforce.
The Typed Ember workforce joins the Framework, Studying, CLI, and Knowledge Core groups as a brand new Core sub-team: the Ember TypeScript Core Crew. Its preliminary members are the present Typed Ember workforce: James Davis (@jamescdavis), Dan Freeman (@dfreeman), and Chris Krycho (@chriskrycho).
The workforce will proceed to do all of the issues they’ve been doing:
- sustaining TypeScript construct integration with
ember-cli-typescriptandember-cli-babel - investing in type-checked templates by way of Glint
- sustaining the neighborhood varieties on DefinitelyTyped (till they’re sundown!)
- offering enter on TypeScript implications for RFCs
- advising the neighborhood about finest patterns with TypeScript and Ember
They may even lead and help the trouble to allow Ember to publish varieties natively, advise and collaborate with the Studying workforce on the work to doc TypeScript as a supported language for Ember, and collaborate on key design questions with the Framework workforce.
From one angle, you possibly can see this as nothing a lot altering, and also you’d be proper: the identical individuals who have led this effort for years will hold doing what they’ve been. From one other, although, this can be a big deal: now we have by no means added a brand new officially-supported language earlier than, and including new Core groups is uncommon! This marks a major shift for Ember. We haven’t made a proper change to our governance in three and a half years, and now we have solely made a handful of those modifications over the entire historical past of the venture. Getting TypeScript proper actually issues to us, and we’re investing accordingly.
We’d additionally wish to take this chance to say because of the various contributors who’ve helped get us right here, and particularly to emeritus workforce members Derek Wickern and Mike North, who did an unlimited quantity of labor to make Ember’s TypeScript story viable and sustainable.
We’re extremely enthusiastic about the way forward for TypeScript in Ember—and we’re simply getting began.
