import-js/eslint-plugin-import

Webpack resolver looks for custom webpack config in packages with jsnext:main

Open

#666 创建于 2016年11月14日

在 GitHub 查看
 (20 评论) (21 反应) (0 负责人)JavaScript (4,946 star) (1,540 fork)batch import
bugenhancementhelp wantedpackage: resolver/webpack

描述

With a .eslintrc like

"settings": {
  "import/resolver": {
    "webpack": {
      "config": "webpack.karma.config.js"
    }
  }
},

when I import

import {takeEvery} from 'redux-saga';

I get the error

 Cannot find module '/path/to/project/node_modules/redux-saga/webpack.karma.config.js

When I remove the jsnext:main entry from the package.json inside node_modules/redux-saga, the error goes away. So I guess the plugin is somehow trying to find a Webpack config inside redux-saga to load resolve configuration for ES6 files? This might be fine, looking for my custom Webpack config does not make sense, though.

贡献者指南

技术栈
javascriptnodejs
领域
toolingbuild systemdeveloper experience
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
ESLint plugin basicswebpack resolverNode.js module resolution
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Investigate the webpack resolver code in the plugin, likely in `resolvers/webpack.js` or similar. The issue suggests that when a package has `jsnext:main`, the resolver incorrectly uses that package's directory to resolve the webpack config path. Look at how the config path is constructed and ensure it uses the project root, not the dependency path. Review the comment thread in the issue for any suggested fixes or discussions.