Do not watch root folders for failed lookup locations and effective type roots

[sheetalkamat]

Fixes #19170

[mhegazy]

@mjbvz can you give this a quick test on the vscode scenario in #19170

[mjbvz]

Thanks for taking a look. Things look much better for tsserver responsiveness now. The log file does still grow fairly large and there are a number of log events for sub node_modules directories, such as build/lib/watch/node_modules:

Info 36810[14:33:46.246] DirectoryWatcher recursive:: Trigger: /Users/matb/projects/vscode/build/lib/watch/node_modules/.staging/fsevents-4d579504/node_modules/readable-stream/lib/_stream_passthrough.js PathInfo: /Users/matb/projects/vscode Project: /Users/matb/projects/vscode/src/tsconfig.json WatchType: Directory of Failed lookup locations in module resolution

Should these be excluded as well?

[sheetalkamat]

Sadly there is no way to exclude that and still keep project upto date.. The watched folder vscode will exist since the module resolution strategy for your project is amd, program is going to lookup files in this folder to resolve module names. Note that even though this is logged, it is not actionable since we eliminate many file additions/removals

[mhegazy]

Adding baseUrl and using moduleResolution: node should make sure that we only look under the source folder and do not walk higher (except for node_modules).