Suggestion

🔍 Search Terms

string exports, arbitrary identifier namespace names

✅ 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 ofTypeScript's Design Goals.

⭐ Suggestion

📃 Motivating Example

Example valid ECMA262 code that fails:

import { "some name" as impt } from 'external';export { impt as "other name" }

See:

https://www.typescriptlang.org/play?ts=5.2.0-dev.20230621#code/KYDwDg9gTgLgBAbzmOBDAznARAC2AG3wjgHdp8ATLOAXyA

💻 Use Cases

Allow TypeScript to support non-identifier export names per ECMA-262 support (tc39/ecma262#2154).