File differs from already included file only in casing: correct casing but relative path

[adamcfranco]

Error TS1149: File name 'C:/Project/frontend/scripts/State.ts' differs from already included file name '../frontend/scripts/State.ts' only in casing.

I've triple checked the casing in our references and the actual files have the correct casing as well. As far as I can tell, this is solely because the relative path uses incorrect casing, or perhaps it's just because of the relative path itself?

It compiles just fine on Mac and Linux, but throws this error on Windows.

[RyanCavanaugh]

This looks like a bug, but we'll need some way to reproduce it. Do you have a zip file or repo or description of the files we could use?

[adamcfranco]

As it turns out, the issue was with a third party module, tsify. Our project was using 1.0.1, and forceConsistentCasingInFileNames wasn't supported until 4.0.0.

[aaybhangu]

I had same issue with one of my component import. I component directory name was historical with same "h" I was trying to import it with capital "H". It should be "
import { GraphDataComponent } from "./historical/graph-data/graph-data.component";" instead of "import { GraphDataComponent } from "./Historical/graph-data/graph-data.component" in app.moudule.ts.

[yurylavrukhin]

Thanks @aaybhangu!

[Iti28]

Hi, I am still facing this issue with - error TS1149: File name 'src/models/headers/userRole.ts' differs from already included file name 'src/models/headers/UserRole.ts' only in casing.
I have tried multiple ways to fix it , but no luck . I am using windows.

[AliceNewzoo]

I am also facing the same issue.
For now, "solved" by setting:
"forceConsistentCasingInFileNames": false,
in tsconfig.json

I stumbled across this exact same error recently.
After doing some googling I found this. The last reply caught my eye. So I simply closed the folder is was working in in Visual Studio Code and re-opened it. After everything loaded up, no errors and I didn't have to mess with the tsconfig.json file.

hope this helps

[github0013]

I came across this same issue

• remove the workspace didn't help
• changing forceConsistentCasingInFileNames didn't help

For my case, somewhere in the directory, the errors were happening, was changed...? So I had to do the following to fix them all.

1. You change the directory name to something like "OriginalDirectoryName" => "AnotherName"
2. VsCode will try to update the directory name in the source, so wait for a few seconds, and it will show all the files need to be updated with the new directory name.
3. Go File -> Save All and save them all
4. Change the directory name back "AnotherName" => "OriginalDirectoryName"
5. Again, it's gonna try to update files, so you save them all.
6. Reboot VsCode.

then it should fix the problem.

[nharrisanalyst]

I am getting this bug after renaming a file from the camelCase to uppercase all first letters