import-js/eslint-plugin-import

Resolvers naming convention for scoped packages

Open

#1,077 建立於 2018年4月12日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)JavaScript (4,946 star) (1,540 fork)batch import
acceptedenhancementhelp wantedresolver

描述

Hi!, thanks for this library, it's super useful. I just published @5rabbits/eslint-import-resolver-directory-named and It would be great if scoped packages follows the eslint-import-resolver-* convention), so that users can include it like this:

settings:
  import/resolver: @5rabbits/directory-named

Currently I'm using the full package name import/resolver: @5rabbits/eslint-import-resolver-directory-named, but it's kinda verbose 😞.

貢獻者指南

技術棧
javascriptnodejs
領域
developer experiencetooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
familiarity with eslint plugin architecture
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
The issue requests supporting a shorthand resolver name for scoped packages (e.g., @scope/resolver instead of @scope/eslint import resolver resolver). Investigate the resolver loading logic in eslint plugin import, likely in the `resolve` or `resolvers` module. Check if there's a pattern for stripping the `eslint import resolver ` prefix. The existing resolvers are loaded by looking for a package named `eslint import resolver <name>`. For scoped packages, the convention should map `@scope/name` to `@scope/eslint import resolver name`. Review the codebase for how resolvers are resolved and consider adding support for scoped packages.