import-js/eslint-plugin-import

`import/no-unresolved` has false positives for search query

Open

#1,739 创建于 2020年4月29日

在 GitHub 查看
 (11 评论) (15 反应) (0 负责人)JavaScript (4,946 star) (1,540 fork)batch import
bughelp wantedpackage: resolver/node

描述

image

Queries are supported: https://nodejs.org/api/esm.html#esm_url_based_paths

Using eslint@6.8.0 and eslint-plugin-import@2.20.2

贡献者指南

技术栈
javascriptnodejs
领域
tooling
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Node.js ESM basicsESLint plugin conceptsimport/no unresolved rule
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
45
研究方向
The issue is that the `no unresolved` rule incorrectly flags imports with query strings as unresolved. The Node.js ESM spec supports query strings, so the resolver needs to strip them before checking file existence. The fix likely involves modifying the resolve function in the import plugin to ignore query strings. The discussion in the issue suggests that a simple `path.split('?')[0]` might suffice, but needs to be integrated into the resolution pipeline.