PR Checklist

• Addresses an existing open issue:fixesBug(website): Acquired types are shown in the editor but not reflected in linting #11120
• That issue was marked asaccepting prs
• Steps inContributing 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 ine57126a

returnvfs.createVirtualTypeScriptEnvironment(

The modules likemonaco,typescript, andtypescript-website are scattered, so it’s a bit confusing

1. createts.program by monace

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

createLanguageService in typescript.link

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

And filenames output bygetScriptFileNames will be added in the code below.
defaults.addExtraLib(code, path) intypescript-website =>defaults.addExtraLib(code, path) inmonaco

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

2. createts.program by TypeScript-VFS.

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

Lines 24 to 31 ine57126a

	constregisteredFiles=newSet<string>();
	constcreateEnv=(
	compilerOptions:ts.CompilerOptions,
	):tsvfs.VirtualTypeScriptEnvironment=>{
	returnvfs.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 thets.Program for both the Editor and Linting

Testing

1. Click alink that already has code pre-filled.
2. Enter code in an empty playground