Skip to content
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

Closed
sebelga opened this issue Jan 27, 2018 · 15 comments
Closed

Casing of <lib> does not match the underlying filesystem #400

sebelga opened this issue Jan 27, 2018 · 15 comments
Labels
info-needed Issue requires more information from poster

Comments

@sebelga
Copy link

sebelga commented Jan 27, 2018

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 👍

@dbaeumer dbaeumer added the info-needed Issue requires more information from poster label Feb 1, 2018
@dbaeumer
Copy link
Member

dbaeumer commented Feb 1, 2018

@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

@sebelga
Copy link
Author

sebelga commented Feb 1, 2018

@dbaeumer I don't get the error in the terminal. Only inside VS studio code.

This is what I get:

alt text

@stoplion
Copy link

+1

@dbaeumer
Copy link
Member

@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?

@sebelga
Copy link
Author

sebelga commented Mar 19, 2018

It is related to my repo I guess because other project using eslint don't have this issue.
The repo with errors is https://github.com/sebelga/gstore-node
I was going to copy/paste all file to new files but didn't have time to do it yet.

@dbaeumer
Copy link
Member

This works for me without problems.

2018-03-19 09_30_53-casing of _lib_ does not match the underlying filesystem issue 400 microsof

@sebelga
Copy link
Author

sebelga commented Mar 19, 2018

Interesting... I did clone the project in an new folder though (I got that far 😄 )...
I will do it again and let you know. Thanks for looking into this 👍

@ValeryVS
Copy link

ValeryVS commented May 4, 2018

@dbaeumer
@sebelga
I also faced with this issue.
And it can be reproduced only in VS Code.
eslint in terminal doesn't show error.

@sebelga
Copy link
Author

sebelga commented May 6, 2018

@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 😄

@dbaeumer
Copy link
Member

dbaeumer commented May 7, 2018

@ValeryVS can you provide me with a GitHub repository I can clone that demos the behavior?

@ValeryVS
Copy link

ValeryVS commented May 7, 2018

Can't share my project's repo, but I will try to reproduce it in fresh project.

@ValeryVS
Copy link

ValeryVS commented May 7, 2018

Actually, my issue is not the same.
I have not Casing of <lib> ... error.
#464

@Hirse
Copy link
Member

Hirse commented May 24, 2018

Looks like this is not an issue (any more), right?

@sebelga
Copy link
Author

sebelga commented May 25, 2018

Yeah, never found out why only 1 of my project with eslint was giving this issue.

@dbaeumer
Copy link
Member

Great. I will close the issue then.

@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 9, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

5 participants