It seems that when eslint-import-resolver-webpack is used in an eslint configuration which lints on import/no-unresolved, that rule will fail on every import when run in jest-runner-eslint. This includes relative import paths, paths from node_modules, as well as the aliased import paths which the resolver is meant to take care of. It doesn't appear to matter what is in the webpack config at all.
I have in my .eslintrc:
"settings": {
"import/resolver": "webpack"
},
Removing this will resolve relative paths and node_modules correctly, but obviously misses aliases.
It seems that when
eslint-import-resolver-webpack
is used in an eslint configuration which lints onimport/no-unresolved
, that rule will fail on every import when run in jest-runner-eslint. This includes relative import paths, paths from node_modules, as well as the aliased import paths which the resolver is meant to take care of. It doesn't appear to matter what is in the webpack config at all.I have in my .eslintrc:
Removing this will resolve relative paths and node_modules correctly, but obviously misses aliases.