import-js/eslint-plugin-import

[import/extensions] ".." and "." import paths are incorrectly flagged as requiring an extension, when either is al local package

Open

#2,844 创建于 2023年7月31日

在 GitHub 查看
 (2 评论) (2 反应) (0 负责人)JavaScript (4,946 star) (1,540 fork)batch import
bughelp wanted

描述

In #2778, we determined that this plugin incorrectly flags ".." and "." import paths, when those imports refer to a local package (with a package.json).

贡献者指南

技术栈
javascriptnodejs
领域
toolingdeveloper experience
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
needs maintainer response
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Understanding of ESLint custom rulesNode.js module resolution
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
The issue references #2778 where a similar case was discussed. To fix, examine the `import/extensions` rule implementation in the plugin, likely in `src/rules/extensions.js` or similar. Investigate how the rule determines whether a path is a local package by checking for a `package.json` in the directory. The fix should ensure that relative paths like '.' and '..' that resolve to a package (with a `package.json`) are not flagged as requiring an extension. Test cases should be added for this scenario.