OpenApr 7, 2026
No due date
•Last updated Dormant issues are defects that still exist as far as we know, but don't warrant additional investment and are not high-priority. This is typically due to one or more factors, such as:
- Requiring an uncommon or discouraged configuration
- Coding patterns that aren't idiomatic TS/JS
- Minimal impact (e.g. error message phrasing that is only wrong in degenerate cases)
- Low likelihood of encounter (e.g. requires very specific and unusual steps to observe)
- Existence of a straightforward workaround
PRs for issues in this milestone are accepted, but will require stronger justification in terms of risk, complexity, and performance cost. Invasive, hard-to-review, or otherwise overly impactful PRs targeting issues in this milestone won't be merged.
57% complete
List view
0 issues of 11 selected
- Status: Open.#58130 In microsoft/TypeScript;
- Status: Open.#31789 In microsoft/TypeScript;
- Status: Open.#34695 In microsoft/TypeScript;
- Status: Open.#62140 In microsoft/TypeScript;
- Status: Open.#56055 In microsoft/TypeScript;
- Status: Open.#55091 In microsoft/TypeScript;
- Status: Open.#62896 In microsoft/TypeScript;
- Status: Open.#63050 In microsoft/TypeScript;
- Status: Open.#63206 In microsoft/TypeScript;
- Status: Open.#63357 In microsoft/TypeScript;
Inside a generic function with a remapped type as parameter, elements are wrongfully inferred as {}.
Status: Open.#63363 In microsoft/TypeScript;