import-js/eslint-plugin-import

Support URL imports

Open

#933 建立於 2017年9月25日

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

描述

With ES modules having landed in Chrome and Safari a few months ago, it would be great to support imports from URLs.

image

Right now, a statement like the above will generate three errors:

'https:' should be listed in the project's dependencies.
Unable to resolve path to module ...
Unexpected use of file extension "js" for ...

貢獻者指南

技術棧
javascriptnodejs
領域
tooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaScriptESLint plugin basicsNode.js module system
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
The issue requests support for URL imports in the eslint plugin import rules. Currently, importing from a URL (e.g., 'https://...') triggers errors about missing dependencies and unresolved paths. To implement this, one should investigate how the plugin resolves imports, particularly in the 'no unresolved' and 'no extraneous dependencies' rules. Look at the import resolution logic in the `resolve` module. Consider adding a check to treat URL imports as external, maybe by checking if the import path starts with 'http://' or 'https://'. There are no linked PRs, but the discussion in the comments may provide additional context. The solution should likely involve modifying the resolver to skip URL imports or treat them as already resolved.