microsoft / microsoft/TypeScript

Review/update https://typescriptlang.org/tsconfig for TS 6.0

Ouverte
#63,392 6 commentaires 0 réactions 1 personne assignée Voir sur GitHub

@RyanCavanaugh y travaille déjà.

Depuis le 14/4/2026.

Docs
Langage dominant
Go
Étoiles
111k
Forks
14.3k
Merge moyen
2 j 4 h
PR mergées (30 j)
132

Description

Acknowledgement
  • I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.
Comment

There is a lot of information on https://typescriptlang.org/tsconfig that's just plain wrong now that 6.0 has been released.

Some things I've noticed so far:

  1. The documentation for the default value of target is currently wrong (at least the "…ES5 otherwise" bit). This section also still mentions ES3 as an allowed target value.

  2. The documentation for types still says:

    By default all visible@types” packages are included in your compilation. Packages in node_modules/@types of any enclosing folder are considered visible.

    But types actually now defaults to [], and @types packages need to be explicitly listed to be included in the global scope.

  3. The paths documentation says:

    A series of entries which re-map imports to lookup locations relative to the baseUrl if set, or to the tsconfig file itself otherwise.

    But I'm pretty sure the first part of that is a lie.

  4. rootDir talks about its default being computed from "the longest common path of all non-declaration input files" (both in the description and the "Default" section on the right side), but really it's just the parent directory of the tsconfig file.

  5. module still refers to amd & umd, but those no longer exist.

There are likely additional things that are outdated; the above was just based on a quick skim.

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.