Allow `infer function return type` refactor when return type are not imported

Suggestion

🔍 Search Terms

"infer function return type"

refactor

✅ 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.

⭐ Suggestion

Infer function treturn type require all types used in return type are imported.
It takes a while to find which field is using a not imported type when returning many values as a object.

I want this refactor allowed by:

a. Auto import missing types
b. Show a message that tell user what is missing
c. Replace not imported type with unknown .

📃 Motivating Example

infer function return type refactor works when there is missing imports

💻 Use Cases

I'm extracting vue code to use composition api, with eslint rule @typescript-eslint/explicit-module-boundary-types enabled.
so i want use this refactor.

But infer function return type is not avaiable because some type not imported.

And i can not view all types because there is too many.

Start by reproducing the infer function return type refactor with a function whose returned object uses types that are not imported. Review the existing refactor behavior and determine which proposed handling is appropriate: auto-importing missing types, reporting them, or replacing them with unknown. Done means the refactor has a defined behavior for missing imports and coverage for the motivating case.