microsoft / microsoft/TypeScript
Feature Request: Make ES module exports conform to an interface using triple slash directive
まだ誰も着手していません。
- 主要言語
- Go
- スター
- 111k
- フォーク
- 14.3k
- 平均マージ
- 2日 4時間
- マージ済み PR(30日)
- 132
説明
Search Terms
ESM, ES module, EcmaScript Module, Interface, Exports, triple slash directive, module
Suggestion
I want to be able to enforce and ESM's exports to conform to an interface.
Here's an ESM that exports some values:

This ESM is going to be consumed by some system; the ESM acts as configuration for that system.
The system could expose interfaces/types for all possible exports, and users apply them manually:

But this is manual work, and thus error-prone.
I propose to be able to do:

The exact syntax TBD.
Adding
/// <exports name="ConfigInterface" from="system-that-needs-configuration" />
will tell typescript about which interface the ESM exports should adhere to and where to find it.
If this is implemented in a triple slash directive this can also work for non-ts files.
Use Cases
I want users of storybook to be able to configure it with ease using modern code.
CommonJS isn't tree-shake-able, which is important to us. There's a pretty detailed RFC for this feature for storybook here: https://docs.google.com/document/d/15aAALZBl0GTBEKgJN219ebzJ8LUJf2TVJ3hQdkNdLvQ/edit#
Tools like babel, eslint & webpack currently are or can be configured using CommonJS modules; as the ecosystem for ESM is improving, being able to add an interface to an ESM becomes really useful.
Tools could start using ESM for configuration more, which has clear benefits over CommoNJS.
Examples
Here's a config file that is annotated with the triple slash directive:

Here's the interface that's being referred to:

This should warn the user that logLevel = 'any' is not a valid value.
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.
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
調査の方向性
ソースファイルもテストのエントリーポイントも指定されていません。まず、提案されている triple-slash directive と ESM の export/interface の例を確認してください。完了条件は、合意された構文と、logLevel = 'any' のような無効な export を報告する検証が用意されていることです。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- javascript, typescript
- 領域
- compilers
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 25/100