Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

import/no-unresolved

See original GitHub issue

I am using the vscode editor and am having problems with eslint validation of false-positive type. My operating system mac os (high sierra).

More details:

Error:

[eslint] Casing of [relative path] does not match the underlying filesystem. (import / no-unresolved)
module "[module path]"

captura de tela 2017-10-13 as 12 34 17

captura de tela 2017-10-13 as 12 34 22

captura de tela 2017-10-13 as 12 34 27

pajzvoej82

"eslint": "^4.8.0",
"eslint-config-airbnb": "^15.0.1",
"eslint-import-resolver-webpack": "^0.8.3",
"eslint-plugin-import": "^2.6.0",
"eslint-plugin-jest": "^21.2.0",
"eslint-plugin-jsx-a11y": "^6.0.2",

Issue Analytics

State:
Created 6 years ago
Reactions:2
Comments:10 (2 by maintainers)

Top GitHub Comments

4reactions

EdwardSaltercommented, Dec 4, 2017

I am seeing this when via command line when running it through a setup similar to how create-react-app works. We have a project that houses our webpack build alongside our application boilerplate. I was seeing the error in this app as well until I upgraded all eslint dependencies and it has now disappeared.

After creating a new app using the boilerplate (which is CRA compatible), the new application suffers this problem. This occurs when running eslint via the build script (which uses eslint-loader inside of webpack) and also when running via command line (npx eslint src). The plugin inside of Atom is not affected by this issue for some reason.

EDIT: I have realised that it is actually an occurrence of #720 as my current working directory in Git Bash did not match the casing of the folder structure on disk. As far as I can tell, #720 should be fixed and is in v2.8.0 but I am still seeing it.

2reactions

mattcleary55commented, Nov 7, 2017

I’m having the exact same issue with Atom.