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

[mkantor]

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.

[mkantor]

This issue's rightful home is probably https://github.com/microsoft/TypeScript-Website/issues, but it doesn't fit the available issue templates there. It's not quite "critical" but IMO seems important to address soonish to avoid undue confusion during the 5 → 6 transition. I also worry it wouldn't have enough visibility if filed there.

Anyway, I'm happy to close this and re-file over there if desired.

[mkantor]

I could take a stab at a pull request, but I feel like a maintainer would do a better job at capturing the nuances, and would have better eyes for catching things I've missed. Maybe I could at least do a first pass though; let me know if that'd be helpful.

[mkantor]

If anyone spots additional items requiring attention, please post them as comments and I'll add them to my list.

[RyanCavanaugh]

I started this at RyanCavanaugh/schemastore#1 but haven't had time to get it over the finish line. Feel free to doublecheck this; it's not fully vetted yet.

[mkantor]

I left a few comments on RyanCavanaugh/schemastore#1, but also I think that pull request will affect defaults & allowed values, but not the description copy on https://typescriptlang.org/tsconfig. The descriptions will need to be separately updated in the https://github.com/microsoft/TypeScript-Website repository, right?

[jonkoops]

I've opened two PRs on the TypeScript-Website repo to address parts of this:

• Update module default value in tsconfigRules TypeScript-Website#3608 — fixes the module default (also fixes [V6] module defaults is not esnext #63330)
• Update moduleResolution default value in tsconfigRules TypeScript-Website#3609 — fixes the moduleResolution default

Both update the defaults in tsconfigRules.ts to match the current compiler logic. Happy to tackle more items from this list if these get merged.