-
Notifications
You must be signed in to change notification settings - Fork 333
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
Casing of <lib> does not match the underlying filesystem #400
Comments
@sebelga does the problem show up if you run eslint from the terminal as well. If so I would recommend to ask the question in this repository: benmosher/eslint-plugin-import |
@dbaeumer I don't get the error in the terminal. Only inside VS studio code. This is what I get: |
+1 |
@sebelga can you provide me with a GitHub repository I can clone that demos this ? Which OS are you on and does the name of the VS Code workspace folder you open match the name on disk in terms of casing? |
It is related to my repo I guess because other project using eslint don't have this issue. |
Interesting... I did clone the project in an new folder though (I got that far 😄 )... |
@ValeryVS well I never managed to understand the cause. What I did realize is that when I cloned the repository to another folder name the problem went away! Extremely strange... I didn't investigate why 😄 |
@ValeryVS can you provide me with a GitHub repository I can clone that demos the behavior? |
Can't share my project's repo, but I will try to reproduce it in fresh project. |
Actually, my issue is not the same. |
Looks like this is not an issue (any more), right? |
Yeah, never found out why only 1 of my project with eslint was giving this issue. |
Great. I will close the issue then. |
Hello
I am getting false positive with the plugin on the rule "import/no-unresolved" in Visual Studio Code.
I get "
Casing of <lib> does not match the underlying filesystem
".But when I run eslint from the command line, I don't get this error.
It is related to import-js/eslint-plugin-import#720 and seems to have been fixed in version 2.8.0 of "eslint-plugin-import" but I still get the error.
I appreciate the help if anyone knows how to fix this in VS Studio Code 👍
The text was updated successfully, but these errors were encountered: