import-js/eslint-plugin-import

Inferred Import Fails But Explicit Import Succeeds

Aperta

#738 aperta il 7 feb 2017

 (0 commenti) (0 reazioni) (0 assegnatari)JavaScript (1549 fork)batch import
help wantedpackage: resolver/webpack

Metriche repository

Star
 (5940 stelle)
Metriche merge PR
 (Merge medio 138g 22h) (3 PR mergiate in 30 g)

Descrizione

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

Guida contributor