Skip to content

No labels!

There aren’t any labels for this repository quite yet.

142 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
Question
Question
An issue which isn't directly actionable in code
1
Recent Regression
Recent Regression
This is a new regression just found in the last major/minor version of TypeScript.
Repro Requested
Repro Requested
Indicates that we'd like a compiler backed repro for this issue: https://aka.ms/ts-repros
Rescheduled
Rescheduled
This issue was previously scheduled to an earlier milestone
243
Revisit
Revisit
An issue worth coming back to
17
Scenario: Monorepos & Cross-Project References
Scenario: Monorepos & Cross-Project References
Relates to composite projects (a.k.a references between "medium sized projects")
8
Source: Telemetry
Source: Telemetry
The issue relates to the telemetry in editors
Spec
Spec
Issues related to the TypeScript language specification
Suggestion
Suggestion
An idea for TypeScript
2,672
Too Complex
Too Complex
An issue which adding support for may be too complex for the value it adds
@types
@types
Relates to working with .d.ts files (declaration/definition files) from DefinitelyTyped
typescript@experimental
typescript@experimental
Pull requests tagged with this label are automatically rebased together with master and published
Unactionable
Unactionable
There isn't something we can do with this issue
Update Docs on Next Release
Update Docs on Next Release
Indicates that this PR affects docs
Visual Studio
Visual Studio
Integration with Visual Studio
17
VS Code Priority
VS Code Priority
Critical issues that VS Code needs fixed in the current TypeScript milestone
3
VS Code Tracked
VS Code Tracked
There is a VS Code equivalent to this issue
70
Waiting for TC39
Waiting for TC39
Unactionable until TC39 reaches some conclusion
8
Website Logo
Website Logo
Deprecated
1
Website
Website
Deprecated - please forward issue to microsoft/TypeScript-Website
2
Won't Fix
Won't Fix
The severity and priority of this issue do not warrant the time or complexity needed to fix it
Working as Intended
Working as Intended
The behavior described is the intended behavior; this is not a bug
1