import-js/eslint-plugin-import
Inferred Import Fails But Explicit Import Succeeds
开放
#738 创建于 2017年2月7日
help wantedpackage: resolver/webpack
仓库指标
- 星标
- (5,939 个星标)
- PR 合并指标
- (平均合并 138天 22小时) (30 天内合并 3 个 PR)
描述
Explicity passing my webpack resolve object means ESLint can correctly resolve aliased paths:
.eslint.js
"settings": {
"import/resolver": {
"webpack": {
"config": {
"resolve": {
"modules": ["app", "node_modules"],
"extensions": [".js", ".jsx", ".css"],
"alias": {
"component-styles": "css/components",
},
}
}
}
}
}
However using configuration that infers paths fails:
.eslint.js
"settings": {
"import/resolver": "webpack"
}
or:
.eslint.js
"settings": {
"import/resolver": {
"webpack": {
"config": "webpack.config.js"
}
}
}
In both cases, paths aren't discovered
Webpack 2.2.0 eslint-plugin-import 2.2.0