Allow export type for module = none

Search Terms

allow export type module none

Suggestion

For "module": "none", please allow export type Foo = { ... }

Use Cases

For ExtendScript code, tsc shouldn't generate export in generated js file.
For ts < 4.0, I can use "module": "ESNext"；for ts >= 4.0，I have to use "module": "none"(in ts 4.0.2，"module": "ESNext" will generate export {}, that is error for Extendscript)，but I cannot use export type ... in "module": "none", I use export type ... to reuse types between Extendscript and browser js code.
This blocks me to upgrade to typescript 4.0

Examples

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, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

まず、"module": "none" と export type 宣言を使用して tsc で問題を再現し、次に "module": "ESNext" および TypeScript 4.0 について説明されている動作と比較します。期待される出力を判断するために、コンパイラーのモジュール処理と declaration emit のテストを確認します。export type が module none で受け入れられ、実行時の export が出力されなければ完了です。