"No inputs were found in config file", when looking at some files within node_modules

[parris]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.96.4
• OS Version: Darwin arm64 23.5.0

When a node_module bundles in a tsconfig file I'll end up getting this error. Most packages do not do this, it makes sense, the tsconfig is really just for builds. BUT occasionally they do bundle it, and when that happens obviously sources can not be found. I'll contact the offending package, but a built in solution would be nice as well since this is a frequent problem - this happens multiple times per year for me.

Example repo: https://github.com/deca-inc/vscode-repro-issue-238768

Steps to Reproduce:

1. Make any basic typescript project, with any package manager
2. Install a package that has a tsconfig.json within it, where the inputs won't be found
3. Import that node_module then try to "meta/command+click" into the definition of that import

Outcome: A "Problem" appears under the Problem tab. There's no way to make this problem go away unless you close the files and close vscode completely.

Possible solutions:

1. Don't look for tsconfig files under node_modules ever
2. Document how to ignore specific offending packages - it's pretty hard to find the answer for this out there on search engines.