May be we also need some tweaking if referenced project was discovered while node_modules were detected and we ignored everything but entry point.

We also could get info from opened referenced project instead of adding to auto import provider but I wanted to first check if we want something like this which understands referenced project or not before adding anything more to this experiment

We also could get info from opened referenced project instead of adding to auto import provider

This was the approach I took in #47690 which ended up being problematic for the export info and module specifier caches. I forgot about this distinction when we talked the other day. I think using the AutoImportProvider is slightly less efficient but avoids these caching pitfalls, and is overall a more promising approach. I spent a little while trying to break the export info cache invalidation on this branch and it looked good. That said, exportMapCache.ts and moduleSpecifierCache.ts could be updated to exercise this new functionality.

@andrewbranch ready for review

@andrewbranch i had missed the editor services to update to check for same flag when i first pushed commit .. didn’t realize you already looked at it or I would I have made separate commit .. i will also add a test when that option is not set in host preferences just for completeness when I get to desk

@sheetalkamat @andrewbranch I am having the problem that autoimport is not working for project references.

Example: project A -> project B
however inside project A autoimport is not finding dependencies inside project B.

Can you point me to some reference /explain how to get this to work?

@joeuy please file a new issue with full repro steps. Thanks!