Issues trying to auto-import across project boundaries

TypeScript Version: 3.2.2, 3.3.0-rc

Search Terms: autoimport, project references, autocomplete

Code Full minimal repro: https://github.com/MLoughry/typescript-repro

See src/a/lib/index.ts

// If another file in the project already has an import from the other project,
//   then attempting to auto-import `bar` will prompt you to import from 'obj/b/lib'
// If no other import is found within the project, no auto-import suggestions are found
console.log(bar);

Expected behavior: Auto-import should work across project boundaries when an outDir is specified (with or without paths specified in tsconfig.json)

Actual behavior:

• If there is already a cross-project import within the project: The auto-import attempts to import from the outDir.
• If there is no other cross-project import within the project: No import suggestions are found.

[MLoughry]

So, there are two issues here: one when the project has no other reference to the module, and another when it does.

Now that @sheetalkamat has laid them out, I can appreciate the perf implications of trying to fix the first issue (project has no other reference to module). However, would there be any perf implications to fixing the other issue (auto-import resolves to outDir file rather than source file)? It seems like just a matter of mapping the outDir path back to the source path, or am I mistaken?

[mikea]

A big issue in our source code base as well. One single source tree with lots of tsconfig.json, all extending single tsconfig.base.json with outDir: "build" & composite: true. References everywhere.

In most cases VSC auto-imports from build/ folder. Need to fix imports manually all the time.