import suggestion from b to sibling a defined in paths compilerOptions about typescript

[RyanCavanaugh]

We're going to need an actual repo to investigate. Speculating, the problem is in the package.json - auto-import will not offer modules that aren't explicitly in your dependencies or devDependencies list, since it's incorrect to depend on a transitive dependency.

[kebeclibre]

Hello, thanks for your answer
I made a mock repo here: https://github.com/kebeclibre/TypeScriptIssue-57762

I explain the steps I take in the commits

I could not reproduce my original problem on our production repo, since the two projects are in two separate repositories and one of them is private.

[RyanCavanaugh]

I don't see a dependency or other hint for to indicate that loading the other project for analysis is valid. Auto-import can only offer imports from files it knows about, and there's no reason it should suspect the peer folder is one it should be looking at.

[kebeclibre]

Yes, precisely.
But when an import preexists in project_b, even if it points to something in project_a that it is not supposed to be aware of, I have a suggestion for that import, and, when hitting F12 to see the definition, it does open the right file.

I'm not sure if it is VSCode or Typescript though.

Cheers anyway and thanks for looking at this

[RyanCavanaugh]

Right. TS isn't scanning your entire hard drive looking for files that might possibly be part of your project; there is obviously some limit. The limit is what you saw. But once you have an import into some other set of files, those files are available for analysis. That's the intended scoping mechanic.