[ID-Prep] Preserve type nodes from type assertions in declarations #57587

The [ID-prep] set of issues aligns Declaration Emit with the forthcoming Isolated Declarations feature.

🔍 Search Terms

declaration emit preserve types assertions

✅ Viability Checklist

• 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 isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

Preserve types from type assertions when emitting declarations.

📃 Motivating Example

// index.ts
type P = {} & { foo: boolean };
export let p = null as P

// index-current.d.ts
export declare let p: {
    foo: boolean;
};

// index-proposed.d.ts
type P = {} & { foo: boolean };
export declare let p: P;

💻 Use Cases

1. What do you want to use this for?
   This would improvement would can bring us closer to external declaration emitters being a reality.
2. What shortcomings exist with current approaches?
   An external tool can extract the type from the assertion, but then they would have different declarations. It would be great if, where possible, typescript would also preserve types as written.
3. What workarounds are you using in the meantime?
   We could force users to always specify the type even when it's obvious from the assertion, but this makes for very frustrating DX