import-js/eslint-plugin-import

Inferred Import Fails But Explicit Import Succeeds

Ouverte

#738 ouverte le 7 févr. 2017

 (0 commentaire) (0 réaction) (0 personne assignée)JavaScript (1 549 forks)batch import
help wantedpackage: resolver/webpack

Métriques du dépôt

Stars
 (5 938 étoiles)
Métriques de merge PR
 (Merge moyen 138j 22h) (3 PRs mergées en 30 j)

Description

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

Guide contributeur