import-js/eslint-plugin-import

Inferred Import Fails But Explicit Import Succeeds

Open

#738 opened on Feb 7, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (1,540 forks)batch import
help wantedpackage: resolver/webpack

Repository metrics

Stars
 (4,946 stars)
PR merge metrics
 (Avg merge 138d 22h) (3 merged PRs in 30d)

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

Contributor guide