Auto importing should choose the nearest one where same symbol name is exported from multiple files

Auto importing should choose the nearest one where same symbol name is exported from multiple files

🔍 Search Terms

auto import
same symbol name

✅ Viability Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

💻 Use Cases

When .vscode/settings.json "typescript.preferences.importModuleSpecifier": "shortest",
The following auto importing behavior is very strange:

// src/app1/config.ts
export const LogLevel=1

// src/app1/main.ts
import {LogLevel} from "src/app2/config"
console.log(LogLevel)

// src/app2/config.ts
export const LogLevel=2

// src/app2/main.ts
import {LogLevel} from "src/app1/config"
console.log(LogLevel)

I think it should auto imports the nearest one, but it auto imports the other one.

When .vscode/settings.json "typescript.preferences.importModuleSpecifier": "relative",
The auto importing behavior is OK:

// src/app1/config.ts
export const LogLevel=1

// src/app1/main.ts
import {LogLevel} from "./config"
console.log(LogLevel)

// src/app2/config.ts
export const LogLevel=2

// src/app2/main.ts
import {LogLevel} from "./config"
console.log(LogLevel)

Reproduce the examples using .vscode/settings.json with importModuleSpecifier set to shortest and relative. Compare the auto-import choices for the two app1/app2 config.ts files, then trace the TypeScript auto-import behavior that ranks candidates; done means shortest mode selects the nearest exported symbol in both cases.