import-js/eslint-plugin-import

[import/extensions] Option to enforce extensions for type-only imports

オープン

#2,530 opened on 2022/08/23

 (6 件のコメント) (0 件のリアクション) (0 人の担当者)JavaScript (1,549 件のフォーク)batch import
help wantedtypescript

Repository metrics

Stars
 (5,940 個のスター)
PR merge metrics
 (平均マージ 138d 22h) (30d で 3 merged PRs)

説明

We have a use case for enforcing the .js extension even on type-only imports (I'm aware this is odd).

This requirement stems from supporting TS users using modules (by specifying "type": "module" in their package.json) and specifying nodenext for moduleResolution options in their tsconfig.

Some context can be gleaned from this PR, where I created a failing test using ^this configuration and proceeded to resolve the errors by adding .js extensions to type-only imports. https://github.com/apollographql/apollo-server/pull/6731

Related: https://github.com/import-js/eslint-plugin-import/pull/2270

Does another option seem reasonable to enforce extensions on type-only imports as well? I'd be happy to open a PR to introduce this if so.

コントリビューターガイド