Find all refs on the module path should show you all imports to it:

Is that not sufficient for your scenarios?

I'm after the opposite—to find all imports for the currently focused module. E.g.:

// a.ts
// "find imports" used in this module will list the imports in `b.ts` and `c.ts`
export const foo = 'bar';

// b.ts
import('./a');

// c.ts
import './a';

I see.. I suppose we can expose this on the export keyword. though it is kinda weird.. possibly another command on the server..

@andy-ms, @amcasey and @DanielRosenwasser thoughts?

@OliverJAsh to confirm, you're not looking for consumers of foo, you're looking for consumers of a.ts?

@mhegazy I agree that it's not clear how we would trigger such a search. Personally, I would expect invoking Find All References on the export keyword to list references to that exported symbol.

Personally, I would expect invoking Find All References on the export keyword to list references to that exported symbol.

yeah.. then a new command is needed, but it wounder if that will be discoverable.