Chris Krycho

We chatted about this a bit and it looks like at least for the US, we only need the first year. That means we don't need to maintain/update it over...

Whoops, didn't mean to close it, sorry—if you want to switch it over to first year, `2011`, *that* we could merge!

@rwwagner90 we discussed this at Framework Core today and agreed that while we think this is definitely a problem worth solving, we *don’t* want to solve it by adding more...

@Alonski thanks for the report, and sorry for the delay. Should be a pretty easy thing to add – please open a PR on DT and we'll get it reviewed...

We discussed this at Framework today and decided to put it into Final Comment Period, with intent to merge it! Thanks, @SergeAstapov!

Sorry for the delay, we agree this is the right path here. CI is likely to be unhappy for unrelated reasons, and I'm going to see if I can get...

Should be unblocked by #1531; I will do the update-branch-and-merge dance once that one lands.

We chatted about this, and we still *super* appreciate the work (three years later 😂) but are going to close it: - We're working on an RFC to switch ember-cli-typescript...

Another use case (recognizing that you have it on the roadmap, and putting it here for search engines mostly): `@types` for specific JS packages. It's pretty often going to be...

@nzakas I'm currently looking at the long-term path for integrating [`ember-template-lint`](https://github.com/ember-template-lint/ember-template-lint) into ESLint, and ember-template-lint has an async API. This is a pretty key part of Ember's move to embedding...