TypeScript cannot find Node globals with default VSCode tsconfig

[bensgilbert]

When scaffolding a VSCode typescript extension with the default tsconfig.json, TypeScript reports missing global names such as console and built-in Node modules like child_process.
This makes the default template uncompilable

{
  "compilerOptions": {
    "module": "Node16",
    "target": "ES2022",
    "outDir": "out",
    "lib": [
      "ES2022"
    ],
    "sourceMap": true,
    "rootDir": "src",
    "strict": true
  }
}

The configuration only includes the "ES2022" library, which does not provide Node.js typings and "types": ["node"], isn't included.

[rinOfTheStars]

One-liner fix (that I can only assume is required due to a bug in VSC, because the typescript docs explicitly say this should not be required) is to add "types": ["*"], to the compilerOptions block of tsconfig.json. No clue if this causes unintended side-effects, but afaik it shouldn't be any different than what the default behavior is supposed to be.