globally declared types are not recognized in the language server unless the file declaring them is opened

[DetachHead]

// foo.ts
declare global {
    const a: number
}

export { }

// bar.ts
console.log(a) // error: Cannot find name 'a'.

to reproduce

1. close foo.ts in vscode
2. restart the deno language server
3. wait for the error to appear in bar.ts
4. open foo.ts and watch the error disappear

vscode's built in typescript language server seems to have the same issue but creating a tsconfig.json file fixes it because it allows it to detect which files to include in the project without having to rely on which files the user opens.

in deno-ts however, doing the equivalent with deno.jsonc does not seem to have any impact.

deno check does not report any error.

workaround

add an import './foo.ts' or /// <reference path="./foo.ts" /> to the top of bar.ts, but this shouldn't be necessary since it should just use the typescript settings in deno.jsonc to determine which files to include in the project

Version: Deno 2.7.11

[bartlomieju]

vscode's built in typescript language server seems to have the same issue but creating a tsconfig.json file fixes it because it allows it to detect which files to include in the project without having to rely on which files the user opens.

You can do the same for Deno, just create a tsconfig.json and point it to that file.

[DetachHead]

from my understanding deno.json is supposed to replace tsconfig.json because that's where all the typescript compiler options are defined?

[bartlomieju]

from my understanding deno.json is supposed to replace tsconfig.json because that's where all the typescript compiler options are defined?

No, that's not correct. deno.json only supports basic compilerOptions; things like paths and other settings are only supported in tsconfig.json.

[DetachHead]

creating a tsconfig.json doesn't seem to have any impact when using deno's language server:

// tsconfig.json
{ "include": ["*.ts"] }

even with this file, i still need to open types.ts in vscode for the errors to go away

[ChristopherMuir]

@DetachHead
That might be independent of the issue. The vscode extension only updates the problem tab when you open files.
denoland/vscode_deno#1269

[DetachHead]

that's a different issue, where diagnostics from files that aren't open don't show up in the problems tab. this is kind of the opposite, where problems in an open file are caused by the fact that another file has not been opened. setting "deno.forcePushBasedDiagnostics": true like you suggested there doesn't fix this issue.