Sublime eslint plugin: "Unable to resolve path to module" while the path exist

Question

In my .jsx module I get this error

Unable to resolve path to module

How can I fix it? The imported module exist.

Do you get the same error report when you run eslint from the command line? Which eslint Plugin do you use? Please add it to your post by editing. — try-catch-finally, May 15 '16 at 12:27
$eslint app/routes.jsx handles without errors, eslint-plugin-import. — VelikiiNehochuha, May 15 '16 at 14:04
I could not resolve this issue, relative paths still show warnings — VelikiiNehochuha, Dec 10 '16 at 14:34
Also having the same issue - if I find a solution, I'll share it. — switz, Oct 01 '17 at 18:28

score 0 · Answer 1 · answered Jan 12 '17 at 06:23

It might be that eslint-import doesn't automatically include the .jsx extension. You can try this:

Add to your .eslintrc:

"settings": {
  "import/extensions": [".js", ".jsx"]
}

If just that doesn't help, try to add eslint-import-resolver-webpack as a devDependency.

npm i -D eslint-import-resolver-webpack

And include it in the .eslintrc settings:

"settings": {
  "import/resolver": "webpack",
  "import/extensions": [".js", ".jsx"]
}

You may need to configure the "module roots" in webpack:

resolve: {
  modules: ['app', 'node_modules']
}

You might need to replace modules by root in webpack 1.x.

If it still don't work (and it does in command line), it might be a sublime linter issue: https://www.npmjs.com/package/eslint-plugin-import#sublimelinter-eslint

1 Answers1