fix(cli): add dom.extras lib

[kitsonk]

Closes: #12558
Fixes: #14344

This adds the lib.dom.extras.d.ts file and modifies the lib.dom.d.ts file to include it. This solves the problem where users use the lib: ["dom", "deno.ns"] configuration when compiling their isomorphic TypeScript and the distributed version of the DOM library does not include every web standard API that Deno supports, and therefore causes confusing errors to the user.

This means we do make a one line edit to the distributed lib.dom.d.ts to include lib.dom.extras.d.ts. This means that users don't have to explicitly include "dom.extras" when using the library, so for most users previous errors will just "go away".

This does establish a pattern now where we can add items Deno supports in advance of the TypeScript distribution supporting it while allowing more isomorphic code to type check safely.

[dsherret]

Nice! This will be good to just work now. I think we should consider this same solution for any similar problems (if they exist)

[jaydenseric]

So if you are publishing a .mjs module that has TypeScript JSDoc types, that is intended to work with type safety both in Node.js and Deno TypeScript projects, that uses DOM globals, how are you supposed to support that?

Do you use triple slash references in the published module? If so, what are the right ones to use now? Do you only add this?

/// <reference lib="dom" />

For deno, do you also need to add this:

/// <reference lib="deno.ns" />

If you do, that will break Node.js TypeScript:

[dsherret]

@jaydenseric would you be able to open a new issue or question on discussions? It’s a better medium than old PRs that are closed.