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 staff devoted to sustaining Ember’s varieties and its TypeScript compiler integrations.
Fortunately, we have already got a bunch of people that do this! For the final 5 years, Ember has had community-driven TypeScript assist, led by the previous and current members of the Typed Ember staff.
The Typed Ember staff joins the Framework, Studying, CLI, and Knowledge Core groups as a brand new Core sub-team: the Ember TypeScript Core Workforce. Its preliminary members are the present Typed Ember staff: James Davis (@jamescdavis), Dan Freeman (@dfreeman), and Chris Krycho (@chriskrycho).
The staff 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 through Glint
- sustaining the neighborhood varieties on DefinitelyTyped (till they’re sundown!)
- offering enter on TypeScript implications for RFCs
- advising the neighborhood about greatest patterns with TypeScript and Ember
They can even lead and assist the hassle to allow Ember to publish varieties natively, advise and collaborate with the Studying staff on the work to doc TypeScript as a supported language for Ember, and collaborate on key design questions with the Framework staff.
From one angle, you may see this as nothing a lot altering, and also you’d be proper: the identical individuals who have led this effort for years will maintain doing what they’ve been. From one other, although, this can be a enormous deal: we have now by no means added a brand new officially-supported language earlier than, and including new Core groups is uncommon! This marks a big shift for Ember. We haven’t made a proper change to our governance in three and a half years, and we have now solely made a handful of those adjustments 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 due to the numerous contributors who’ve helped get us right here, and particularly to emeritus staff members Derek Wickern and Mike North, who did an infinite 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.
