Any problem can be solved by flags, except for the problem of having too many flags

Relates to the public API for TypeScript

Author: Contributor

Awaiting More Feedback

This means we'd like to hear from more people who would be helped by this feature

A fix for this issue is blocked on another fix being in place

Breaking Change

Would introduce errors in existing code

A bug in TypeScript

Deprecated - use "Working as Intended" or "Design Limitation" instead

This issue contains a lengthy and complete description of a particular problem, solution, or design

Relates to checking JavaScript using TypeScript

The team has roadmapped this issue

Community Tooling

This might be better handled by tooling from the community instead of built into TypeScript

For flagging bugs which are compiler or service crashes or unclean exits, rather than bad output

The issue was declined as something which matches the TypeScript vision

Design Limitation

Constraints of the existing architecture prevent this from being fixed

Notes from our design meetings

Issues which may not have code impact

Docs Meeting Notes

Write-ups on the meeting every two weeks on docs topics

The issue relates to how you learn TypeScript

Domain: --incremental

The issue relates to incremental compilation

Domain: Auto-import

Domain: Big Unions

The root cause is ultimately that big unions interact poorly with complex structures

Domain: Comment Emit

The issue relates to the emission of comments when compiling

Domain: Completion Lists

The issue relates to showing completion lists in an editor

Domain: Conditional Types

The issue relates to conditional types

Domain: Contextual Types

The issue relates to contextual types

Domain: Control Flow

The issue relates to control flow analysis

Domain: Declaration Emit

The issue relates to the emission of d.ts files

Domain: Decorators

The issue relates to the decorator syntax

Domain: Error Messages

The issue relates to error messaging

Domain: ES Modules

The issue relates to import/export style module behavior

Domain: Excess Property Checking

Domain: Formatter

The issue relates to the built-in formatter

Domain: Index Types

Issues with `keyof`

Domain: Indexed Access Types

The issue relates to accessing subtypes via index access

Domain: JavaScript

The issue relates to JavaScript specifically

Domain: JS Emit

The issue relates to the emission of JavaScript

Relates to JSDoc parsing and type generation

Domain: JSX/TSX

Relates to the JSX parser and emitter

Domain: lib.d.ts

The issue relates to the different libraries shipped with TypeScript

Domain: Literal Types

Unit types including string literal types, numeric literal types, Boolean literals, null, undefined

Domain: Mapped Types

The issue relates to mapped types

Domain: Organize Imports

Issues with the organize imports feature

Domain: Outlining

Relates to multi-line regions that editors can collapse

Domain: Performance

Reports of unusually slow behavior

Domain: Quick Fixes

Editor-provided fixes, often called code actions.

Domain: Quick Info

e.g. hover text, tool-tips, and tooltips.

Domain: Refactorings

e.g. extract to constant or function, rename symbol

Domain: Related Error Spans

Specifying regions for error messages/diagnostics on multiple locations.

Domain: Signature Help

Information in editor tooltips when invoking a function call

Domain: Smart-Select

Range expansion APIs for editors

Domain: Smart Indentation

Automatic indenting after a newline (not quite formatter/formatting)

Domain: Symbol Navigation

Relates to go-to-definition, find-all-references, highlighting/occurrences.

Domain: This-Typing

The issue relates to providing types to this

Domain: Transforms

Relates to the public transform API

Issues related to build mode

Domain: tslib and Helper Functions

Domain: TSServer

Issues related to the TSServer

Domain: Type Display

Bugs relating to showing types in Quick Info/Tooltips, Signature Help, or Completion Info

Domain: Type Inference

Related to type inference performed during signature resolution or `infer` type resolution

Domain: Variance Relationships

The issue relates to variance relationships between types

An existing issue was already created

Effort: Difficult

Effort: Moderate

Should be feasible

New featurers for ECMAScript (a.k.a. ESNext)

Relates to the ES6 Spec

Relates to the ES7 Spec

Relates to the ES2017 Spec

Relates to the ES2018 Spec

Relates to the ES2019 Spec

Experience Enhancement

Noncontroversial enhancements

A fork with an experimental idea which might not make it into master

Experimentation Needed

Someone needs to try this out to see what happens

Relates to another program, environment, or user action which we cannot control.

feature-request

A request for a new feature

A PR has been opened for this issue

Fixed in TSJS repo

Fix merged in https://github.com/Microsoft/TSJS-lib-generator, but not ported yet

A PR has been merged for this issue

For Backlog Bug

PRs that fix a backlog bug

For Milestone Bug

PRs that fix a bug with a specific milestone

For Uncommitted Bug

PR for untriaged, rejected, closed or missing bug

good first issue

Well scoped, documented and has the green light

This issue has compiler-backed repros: https://aka.ms/ts-repros

You can do this

Housekeeping PRs

(Ping PDostalek) Internationalization/translation of messages in the compiler.

Impact: Bad Emit

Impact: Failed LS Operation

Impact: Incorrect Inference

Not yet reached consensus

Issue relates to TypeScript team infrastructure

Bad-faith PRs, Hacktoberfest spam

Is in active investigation

Just Throw Hindley-Milner At It

I want the type system to leverage some sort of unification-based inference

PR modifies files in the `lib` folder

An issue about the team, or the direction of TypeScript

Needs Investigation

This issue needs a team member to investigate its status.

Needs More Info

The issue still hasn't been fully clarified

This issue needs a plan that clarifies the finer details of how it could be implemented.

This behavior is one of several equally-correct options

This idea sits outside of the TypeScript language design constraints

Paths in Generated import(...)s

Poor Paths in import(...) types.

Iteration plans and roadmapping

PursuitFellowship

Help wanted from Pursuit fellowship; others please avoid until Dec 19

An issue which isn't directly actionable in code

Recent Regression

This is a new regression just found in the last major/minor version of TypeScript.

Repro Requested

Indicates that we'd like a compiler backed repro for this issue: https://aka.ms/ts-repros

This issue was previously scheduled to an earlier milestone

An issue worth coming back to

Scenario: Monorepos & Cross-Project References

Relates to composite projects (a.k.a references between "medium sized projects")

Source: Telemetry

The issue relates to the telemetry in editors

Issues related to the TypeScript language specification

An idea for TypeScript

An issue which adding support for may be too complex for the value it adds

Relates to working with .d.ts files (declaration/definition files) from DefinitelyTyped

typescript@experimental

Pull requests tagged with this label are automatically rebased together with master and published

There isn't something we can do with this issue

Update Docs on Next Release

Indicates that this PR affects docs

Integration with Visual Studio

VS Code Priority

Critical issues that VS Code needs fixed in the current TypeScript milestone

VS Code Tracked

There is a VS Code equivalent to this issue

Waiting for TC39

Unactionable until TC39 reaches some conclusion

Deprecated - please forward issue to microsoft/TypeScript-Website

The severity and priority of this issue do not warrant the time or complexity needed to fix it

Working as Intended

The behavior described is the intended behavior; this is not a bug

No labels found. Sorry about that.