import-js/eslint-plugin-import
Inferred Import Fails But Explicit Import Succeeds
オープン
#738 opened on 2017/02/07
help wantedpackage: resolver/webpack
Repository metrics
- Stars
- (5,938 個のスター)
- PR merge metrics
- (平均マージ 138d 22h) (30d で 3 merged PRs)
説明
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