'File name differs from already included file name only in casing' on relative path with same casing

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?

The thing is, it compiles just fine on Mac and Linux, but throws this error on Windows.

If it helps, forceConsistentCasingInFileNames is enabled in the tsconfig, and we're using tsify to compile.

28 Answers

Solution 1 (worked for me)

The issue occurred when I quickly renamed a file from someFile.ts to SomeFile.ts. Restart your IDE (Visual Studio Code) and the warning will go away.

Solution 2

If you created your file in uppercase and import it in lowercase, the problem still occurs, so check the spelling of the file first.

That's a weird error that occurred in my IDE, but it can be simply done with two simple steps:

rename your file (not component) to another name and once again back to your original name.

Example:

consider we have a myFile.js file in the components directory:

> src > components > myFile.js

First

Rename myFile.js into another name (anything) like temp.js:

myFile.js ----> temp.js

Second

back to its original name,

temp.js ----> myFile.js

It's also work fine with *.ts *.tsx *.js *.jsx extensions.

In my case, the error was in the import statement. The import statement had a capital letter instead of small letter, which worked during develop in Windows, but not when compiling for production.

wrong:

import {SomeClass} from '/some/path/SomeClass.ts';

correct:

import {SomeClass} from '/some/path/someClass.ts';

You need to disable the "forceConsistentCasingInFileNames" in the tsconfig.json file.

So you should have something like that:

{ "compilerOptions": { ... "forceConsistentCasingInFileNames": false, ... } }

For VS Code IDE users:

You can fix it by opening the Command Palette (Ctrl+Shift+P) --> Select Typescript: Restart TS server.

Restarting VS Code IDE didn't work for me and I didn't want to change config files. These are the steps that worked for me to resolve this problem:

From VS Explorer, rename the problem file to a new name
Change the component name to the new name inside the file
Save the file
Restart VS Code
Rename the file back to the name I originally wanted
Change the component name to match

It must be some kind of caching issue inside VS Code

Mine was a vue problem, I removed the .vue extension and it worked

It's not enough to restart your TS server!

As of 2023, I found a consistent way to reproduce the issue. This error will happen whenever you still have imports pointing to the wrong path! (after renaming)

// Wrong path, but same "Already included file name" error import { Home } from './home'; // CORRECT path, but same "Already included file name" error import { Home } from './Home'; // <- new path

Fix all imports path and restart your TS server (on VS Code, press F1 > Restart TS server)

TS team should definetly work on improving this error message :)

When two files exist in same folder with names like a.tsx and A.tsx you will get this error

Ok, just need to throw in my "solution" here as well, since it was different from the others. The error message clearly said where it saw an error. It was the casing of a directory that had been renamed (from Utils -> utils). Even though it was renamed correctly everywhere I still got the error. My solution was to rename it once more (why not, hehe) to utils2. After that it worked fine

For VS Code, only thing worked for me was to clear editor history:

Press Ctrl + Shift + P.
type command Clear Editor History.
Press Enter.

For me the problem only went away:

Close VS Code
Deleting the node_modules\.cache folder.
Re-open VS Code

Even after changing cases and making git config ignore case false(git config core.ignorecase false) still I had to follow the following then only it worked as expected!

git rm -r --cached . git add --all . git commit -a -m "Versioning untracked files" git push origin master

Thanks to this comment:

This is the ONLY solution that worked for me!

OS: windows
IDE: VSCode
Project: React + jsconfig.json

The Case Problem

So I had a FOLDER! renamed, not a FILE!. Major difference !
Consider the following folder structure:

*** INITITAL STATE - BEFORE RENAMING *** |-Highcharts | |___ BarChart | | | |__ index.jsx | |__ getBarChartOptions.js * * * * * *

Next thing I did was to rename "Highcharts" to "highcharts", and things started to get nasty. That error popped-up like crazy. That ONE LETTER going from uppercase to lowercase drove it mad!
One place where that lint error came from was a relative import within index.jsx that called getBarChartOptions.js.

// The insides of the index.jsx file import { getOptions } from './getBarChartOptions'; . . .

Solution - The trick that did it:

As someone here said, You need to rename your file (folder in my case) to another name, and once again back to its original name.
BUT !!!
IF it is a folder? You also NEED to rename OTHER SUB-FOLDERS along the way! It's a RECURSIVE PROCESS if you also have sub-folders! So in my case I also had to rename BarChart (look at the folder tree above) as well to another name, and once again back to its original name, before the error went away completely. Changing the root cause folder (highcharts in this case) was simply not enough. I sincerely hope that it would help someone else out there.

As @Roslan Korkin alluded to, the issue seems to be a bug with the TS server. You can resolve it by turning off the forceConsistentCasingInFileNames option in the tsconfig.json file. But you may still want to have that option turned on.

In that case, follow these instructions:

In the tsconfig.json file, set forceConsistentCasingInFileNames to false
Stop the server if running.
Revert to the original option, forceConsistentCasingInFileNames to true
Restart the server

For me, this was because I had accidently uppercased one of my routes, i.e. Positive instead of positive and then corrected it. However, SvelteKit still had the old version cached. So what you need to do is:

Delete the .svelte-kit/types/src/routes/path/to/your/Route folder. This will remove the old, wrong types.
Run npm run dev to make SvelteKit generate the new, correct types.

Hope this helps!

In my case error was :

File name 'c:/Users/yourUserName/projectName/src/Components/Navbar/Navbar.jsx' differs from already included file name 'c:/Users/yourUserName/projectName/src/Components/Navbar/navbar.jsx' only in casing. The file is in the program because: Root file specified for compilation Imported via "./Components/Navbar/Navbar" from file 'c:/Users/userName/projectName/src/App.js ts1149)

I always keep the directory name starting with a smaller character and file name starting with a capital character.
However this time I kept it identical. I updated it as per the aforementioned statement.
And then just restarting the IDE solved the error msg.

Update : Later I figured out small and capital chars doest matter. Just restarting the IDE also works fine.

The answer was that we were using tisfy 1.0.1, when forceConsistentCasingInFileNames wasn't supported until 4.0.0. Updating fixed the issue.

I've tried these two ways:

Import file with '@/frontend/scripts/State.ts' instead of '../frontend/scripts/State.ts'. It works only if you are using path alias.
Rename the directory of the project and open the project from the new directory.

I had the same issues but it came from the imports inside test files (which were based on jest). Solution was to clear the jest cache using the following command.

 node ./node_modules/jest/bin/jest.js --clearCache

In my case, i have made the changes locally on windows and my git was configured to ignore the casing changes to filenames. When these changes went into the CI Build on linux machine using GitHubActions, it finds the new path in file imports, but does not find the matching files with exact path name(case-sensitive).

Solution in my case was to use git config core.ignorecase false So that git detects such changes and prompts us to push.

I had 2 files that started with the same name

 | |-PcComponentCard.vue |-PcComponentCardList.vue

Fixed my problem by changing one of the names:

 | |-PcCard.vue |-PcComponentCardList.vue

For me the problem was that some folder higher in the folder structure (not the filename itself) was capitalized in Windows and everywhere it was referenced in my njsproj file but not in my import statements. I had to make those 3 sources consistent.

React Js

Error :-

Resolve:-

You can try rename your file 'not component' to another name and once again

back to your original name.

Example:

consider we have a Register.jsx rename to RegisterForm.jsx

from

result

Using VS Code on a Mac in Dec 2023, my casing does not differ but the error goes away when I first focus on the file with the error in the Explorer and then click on the file it says it can't find.

If nothing works try: