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.