ESLint does not work with webpack import resolver in 2017.3
In our project I have ESLint rules set up such that it uses webpack to resolve AMD modules.
On version 2017.3 of both IntelliJ and WebStorm, ESLint shows "import/no-unresolved" error.
It was working fine in 2017.1 versions of IntelliJ and WebStorm and still is working fine if I run ESLint manually for the terminal.
Please let me know if you need anything else from me to troubleshoot this issue.
Please sign in to leave a comment.
Sounds strange... Normally the errors reported by ESLint are the same when using the integration and when running in terminal. Please share a sample project I can use to recreate the issue. I don't need your source files - it can just be a pair of dummy js files with imports; but configuration (package.json, eslint configs, webpack config, etc.) should be the same
Please see https://youtrack.jetbrains.com/issue/WEB-30497 - does it look similar?
Yes, https://youtrack.jetbrains.com/issue/WEB-30497 looks similar. Also, this one is similar too: https://youtrack.jetbrains.com/issue/WEB-30457
Until the fix becomes available as an update, I added the following line to the top of my .eslintrc.js file:
Updated:
Rollback to 2017.3.1 or use the solution from Wouter van Vliet (above)