Skip to content

[QUEST] RFC 800: TypeScript Adoption Plan Implementation Tracking #20162

@chriskrycho

Description

@chriskrycho

RFC 0800 Tracking Issue

Implement RFC 0800: TypeScript Adoption Plan.

Enable TS blueprints

Publish types

We do not need to publish types for every package in Ember's dependencies—only for the packages which are part of its programmatic public APIs. An example of a dependency we don’t need to ship types with: ember-cli-dependency-checker is integrated into the classic Ember CLI build pipeline, but it doesn’t expose any APIs for users to call. The following list is comprised of the items in the default blueprints filtered for that criteria.

These items will be checked off if they have been "claimed"—please comment if you'd like to claim one! We will track their status via links to the issues/PRs which implement them.

Status: Last updated 2022/12/13, with the dependencies from the app and v1 addon blueprints.

Footnotes

  1. Debatably, anyway: we could work on dropping this instead, and its public API usage is intended to be minimal; but right now it is a public API.

Metadata

Metadata

Assignees

No one assigned

    Labels

    TypeScriptWork on Ember’s types

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions