PR Checklist

• Addresses an existing open issue: fixes Bug(website): Acquired types are shown in the editor but not reflected in linting #11120
• That issue was marked as accepting prs
• Steps in Contributing were taken

Overview

I think this issue occurs because of differences in the properties used when creating a ts.Program between Monaco and TypeScript-VFS.

typescript-eslint/packages/website/src/components/linter/createParser.ts

Line 29 in e57126a

return vfs.createVirtualTypeScriptEnvironment(

The modules like monaco, [typescript]
(https://github.com/microsoft/TypeScript), and typescript-website are scattered, so it’s a bit confusing

1. create ts.program by monace

When monaco-editor creating this code will excute link
private _languageService = ts.createLanguageService(this);

createLanguageService in typescript. link

const rootFileNames = host.getScriptFileNames().slice();
 // some code
const options: CreateProgramOptions = {
  rootNames: rootFileNames,
  options: newSettings,
  host: compilerHost, 
  oldProgram: program,
  projectReferences,
};
program = createProgram(options);

And filenames output by getScriptFileNames will be added in the code below.
defaults.addExtraLib(code, path) in typescript-website => defaults.addExtraLib(code, path) in monaco

So, when creating a ts.Program, the rootNames array includes some libraries, such as Node or React.

2. create ts.program by TypeScript-VFS.

typescript-eslint/packages/website/src/components/linter/createParser.ts

Lines 24 to 31 in e57126a

	const registeredFiles = new Set<string>();
	const createEnv = (
	compilerOptions: ts.CompilerOptions,
	): tsvfs.VirtualTypeScriptEnvironment => {
	return vfs.createVirtualTypeScriptEnvironment(
	system,
	[...registeredFiles],

Unlike case 1 above,We don't pass the name of a node_modules folder in fileNames.

In the sentence above, I modified it so that rootNames are provided when creating the ts.Program for both the Editor and Linting