Find all references across project references

Bug Report

🔎 Search Terms

references
find all references
rename

🕗 Version & Regression Information

⏯ Playground Link

💻 Code

These are more scenarios from investigations of #42976 where the definition is considered local but is exported and can be referenced by other projects. So we need to think about a way to figure that out efficiently.

/// /shared/src/index.ts
const local = class {
  foo: string;
  constructor() {
    this.foo = "foo";
  }

  fly() {
    console.log(this.foo);
  }
};
export const d = local;
class xy {
  foo: string;
  constructor() {
    this.foo = "foo";
  }

  fly() {
    console.log(this.foo);
  }
};
export { xy };

🙁 Actual behavior

fly usage from project referencing the shared does not load other projects

🙂 Expected behavior

fly usage from project referencing the shared should load other projects

Beginne damit, das im Issue gezeigte project-reference-Szenario anhand des Beispiels shared/index.ts und eines referenzierenden Projekts zu reproduzieren. Vergleiche das Verhalten von find-all-references für die exportierte lokale Klasse und die exportierte xy-Klasse; der Fix ist vollständig, wenn die fly-Nutzung aus dem referenzierenden Projekt Referenzen aus anderen Projekten lädt.