Labels

Issues with the organize imports feature

Relates to multi-line regions that editors can collapse

Editor-provided fixes, often called code actions.

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

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

Information in editor tooltips when invoking a function call

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

Range expansion APIs for editors

Non-error squiggles that appear in the editor suggesting that you should do something

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

Issues related to the TSServer

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

The issue relates to mapped types

How to turn an import specifier into a .d.ts, .ts, or .js file on disk

Poor Paths in import(...) types or declaration emit

Related to node support in some way

Like ES Modules, but specific to Node.js support (cts, cts, mjs, mts)

The parser didn't handle the syntax correctly

Reports of unusually slow behavior

Specifying regions for error messages/diagnostics on multiple locations.

Fallback label when we just can't figure anything else out

The issue relates to providing types to this

Issues related to build mode

The issue relates to incremental compilation

An existing issue was already created

Good issue if you're already used to contributing to the codebase. Harder than "good first issue".

Good luck.