Cannot export a value if re-exporting a type with same name

[paul-marechal]

Bug Report

TypeScript usually allows exporting values and types with the same name.

// a.ts
export const a = 1
export type a = string

But it doesn't work when re-exporting a type from a third-party library and exporting an arbitrary value at the same time.

// b.ts
export const a = 1
export type { a } from './a'  

🔎 Search Terms

export type re-export error

🕗 Version & Regression Information

• Bug present in 4.1.3
• This is the behavior in every version I tried, and I reviewed the FAQ for entries about re-export

⏯ Playground Link

https://codesandbox.io/s/misty-field-16f9f?file=/src/index.ts

💻 Code

export type { A } from "./a";
export const A = Symbol("A");

🙁 Actual behavior

Error:

Cannot redeclare exported variable 'A'. ts(2323)

🙂 Expected behavior

I would expect this to work since the re-exported name is purely a type.

[DanielRosenwasser]

I think this is working as intended. Import/export aliases can't merge with local declarations in TypeScript. What's more, export type doesn't strictly import the type side of things, it only restricts the things you can do with that import to type-like positions, so even if we wanted to ease the restriction just for export type, we still couldn't.

See

• Design Meeting Notes, 9/13/2019 #33422
• Prevent collision of imported type with exported declarations in current module #31231
• Importing a type with same name as an export #31031

[paul-marechal]

Import/export aliases can't merge with local declarations in TypeScript.

Should this limitation on merging behavior be documented in the appropriate section of the official documentation?

[typescript-bot]

This issue has been marked 'Working as Intended' and has seen no recent activity. It has been automatically closed for house-keeping purposes.