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

Inizia riproducendo lo scenario di project-reference mostrato nell’issue, usando l’esempio shared/index.ts e un progetto che lo referenzia. Confronta il comportamento di find-all-references per la classe locale esportata e la classe xy esportata; il fix è completo quando l’uso di fly dal progetto che la referenzia carica i riferimenti da altri progetti.