[import/no-duplicates] `{"prefer-inline": true}` does not work · import-js/eslint-plugin-import#2715

(14 comments) (13 reactions) (0 assignees)JavaScript (4,946 stars) (1,540 forks)batch import

bughelp wantedtypescript

説明

version 2.27.5

https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/no-duplicates.md#inline-type-imports The documentation states that adding {"prefer-inline": true} as shown below will cause errors and autofixes if there are duplicate imports. However, this was not possible in my environment.

{
  "import/no-duplicates": ["error", {"prefer-inline": true}],
}

It should look like the following, but there is no error or anything.

import NextErrorComponent from 'next/error';
import { type ErrorProps } from 'next/error';
// ↓
import NextErrorComponent, { type ErrorProps } from 'next/error';

Is this currently being corrected?

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

技術スタック: javascripttypescriptnodejs
領域: toolingdeveloper experience
Issue 種別: bug
難度: 3
推定時間: 1-3 hours
活動状況: active
明確さ: clear
前提条件: Basic ESLint configurationTypeScript import syntax
初心者向け度: 70
調査方針: Review the `no duplicates` rule implementation in the eslint plugin import repository, specifically how the `prefer inline` option is handled. Look at the rule's source file (likely `src/rules/no duplicates.js`) and its tests. Check if there are any existing PRs or issues addressing this. The documentation mentions inline type imports, but the actual behavior may not merge duplicate imports as expected. Focus on the logic that merges imports and how the option affects it.