--unstable-node-globals fails with --check option

[SebastienGllmt]

To support libraries that use node global variables, a new --unstable-node-globals variable was added in #26611

However, using this flag with the --check flag fails because Typescript (and the IDE) isn't aware of this flag

Ex: if you have the following code

type Foo = Buffer;

It will fail with

TS2580 [ERROR]: Cannot find name 'Buffer'.
type Foo = Buffer;

This can be fixed by adding the following to your project

declare global {
  type Buffer = typeof import("node:buffer").Buffer;
}

Or (possibly?) with specifying some lib settings. Ideally somehow Deno would know to make this work if you use the flag (but I don't see how the IDE could know this), or at least make a more useful error message that tells you to change your deno.json file to fix this error

[dsherret]

In this scenario, we need to call ts.deno.setNodeOnlyGlobalNames again and provide a new set of globals:

https://github.com/denoland/deno/blob/12b377247be2b74155ded3a678ff2996ef3d7c9f/cli/tsc/99_main_compiler.js#L1344C11-L1344C33

[SebastienGllmt]

This can be fixed by adding declare global to your project

I actually think this is not a great solution because of this JSR issue where JSR doesn't support declare global yet: #23427