-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eslint-import-resolver-webpack not resolving imports when using resolve.modules #510
Comments
grahamb
added a commit
to sfu/snap
that referenced
this issue
Aug 22, 2016
Is your config file a function? I don't think that's supported ATM. |
Which config file, eslint or webpack? .eslint is JSON, webpack is a function that returns the config object. This is a valid way of configuring Webpack 2. |
Adding a simple
… after the config is |
👍 that would be great! |
PR #533 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Per the request in #352 (#352 (comment)) to open a new issue…
webpack version: 2.1.0-beta.21
eslint: 3.3.1
eslint-plugin-import: 1.14.0
eslint-import-resolver-webpack: 0.5.1
I have configured Webpack's
resolve.modules
property as follows:Full webpack.config.js file
.eslintrc file
Project's file structure:
In
client/components/App/index.js
I'm importing another module fromclient/components
withimport UserBio from 'components/UserBio'
. This works, but eslint is throwing animport/no-unresolved
error.Output from running
DEBUG=eslint-plugin-import:* $(npm bin)/eslint client/components/App/index.js
: https://gist.github.com/grahamb/9f7ad28563af2c5a7fcece5f251a96d3The text was updated successfully, but these errors were encountered: