Name overload term/type module re-export as namespace

Suggestion

🔍 Search Terms

I wasn’t sure what terms to be searching for this.

✅ 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

Currently this is possible:

export type A = 1
export namespace A {
  export const foo = 2
}

import { A } from './a.js'

console.log(A.foo)
const A: A = 2 // type errror

However this is not possible:

export type A = 1
export * as A from './something/else/somewhere/else.js'

📃 Motivating Example

I want to be able to reuse a name for a type and namespace for more streamlined downstream usage.

💻 Use Cases

All the same use-cases there already are today for namespace name overloading between terms/types.

[cruhl]

I have been trying to get something like this working for literal years now.

It would dramatically help write better functional/Rust-module-style code.

[MartinJohns]

I believe this to be a duplicate of https://github.com/microsoft/TypeScript/issues/48764#issuecomment-1102818406.