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

Question

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.

In my case it was the case, (used uppercase instead of lower case) — 27px, Dec 31 '20 at 11:25

score 113 · Answer 1 · answered Jun 02 '20 at 19:08

113

For me, the issue occurred when a file was quickly renamed from someFile.ts to SomeFile.ts. Restarting my IDE (Visual Studio Code) made the warning go away.

answered Jun 02 '20 at 19:08

Paul Razvan Berg

10,820
7
50
86

4

Usually for stuff like this Reload Window works for me, but in this case a full restart of VS Code was needed – Jack Barry Mar 05 '21 at 17:55
2

I had to do a full restart – SujithaW Jul 30 '21 at 14:23
1

Same... Restarting did the trick – Luke Savefrogs Dec 21 '21 at 15:44
I did the same thing as op, but for Vetur, it does not go away even after I restart vscode – Darky WC Apr 27 '22 at 03:08
it's work fo me, tnx – al.koval May 05 '22 at 07:46

score 76 · Answer 2 · answered May 03 '19 at 09:29

76

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';

answered May 03 '19 at 09:29

Martin Åhlin

2,102
18
27

This answer is the correct one. – Birhan Nega Sep 26 '21 at 08:40
thats the one. thanks – testingtestinganyone Oct 10 '21 at 15:01

nima · Answer 3 · 2022-01-21T11:28:54.777

47

UPDATE 2021

That's a wired 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.

edited Jan 21 '22 at 11:28

answered Feb 15 '21 at 09:32

nima

6,005
8
32
48

5

You're literally my hero. Thank you! – Barry Michael Doyle Jul 21 '21 at 12:21
2

@novonimo, You're my hero too, thanks bro! – AmerllicA Oct 16 '21 at 16:18
2

Yep it works thanks HERO LOL – zt1983811 Jan 24 '22 at 02:55
1

What I've just discovered, removing extension in component import statement also helps. Can't figure it out why, yet. – Filip Górczyński Apr 01 '22 at 05:37
2

I did the solution similarly as op, but just reload my vscode after renaming the file. Then revert its name after reload, and it works for Vetur. – Darky WC Apr 27 '22 at 03:13

score 36 · Answer 4 · answered Dec 27 '19 at 13:53

36

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

So you should have something like that:

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

answered Dec 27 '19 at 13:53

Ruslan Korkin

2,460
1
24
20

for some reason in my dev environment, it was working fine by default, but in production-build (Docker, alphine-linux) it was bugging. I found that making this flag to true, makes it consistently bugging, which is what I want. :) Thanks! – Aidin Dec 20 '21 at 21:24

score 30 · Answer 5 · answered Sep 01 '20 at 14:11

30

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

answered Sep 01 '20 at 14:11

ttemple

1,531
1
14
12

3

In my case I just renamed the file then renamed it back again – Fabricio Mar 13 '21 at 21:51
Same here, renaming the file and then make it back again worked for me as well. tnx – Ali Afsahnoudeh Aug 02 '21 at 12:42
Same, renaming the file. Weird issue. – Danny Sep 14 '21 at 21:24
In my case it was ComponentName.Vue vs. ComponentName.vue (upper and lower case V). Everything appeared lowercase as intended but still the error. The steps above worked. Thanks – user2721180 Nov 09 '21 at 19:29

score 14 · Answer 6 · answered Oct 21 '21 at 04:19

14

For VS Code IDE users:

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

answered Oct 21 '21 at 04:19

mcjai

208
2
7

score 9 · Answer 7 · answered Oct 05 '20 at 09:17

9

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

answered Oct 05 '20 at 09:17

james ace

1,693
18
10

1

in case anyone else has the same problem in Vue, I can vouch this solves the error, at least in Vue3. – nos codemos Oct 10 '20 at 11:25
This actually works. Have you any idea why? This has to go down as one of the weirdest bugs to ever walk this earth, lol. – Igiri David Sep 07 '21 at 17:42

score 5 · Answer 8 · answered Mar 17 '21 at 13:46

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

score 4 · Answer 9 · answered Mar 27 '20 at 01:07

4

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

answered Mar 27 '20 at 01:07

Dinesh Khetarpal

359
2
5

This was the case for me. I had app.js and App.test.js and was getting this error when importing from app.js- 'app.js' differs from already included file name '/src/App.js' only in casing. ts(1149) Lowercasing App.test.js fixed it. – Steve Nov 03 '20 at 20:46
Same for me. For some reason duplicated files were only present in github and heroku was failing on build with this error. Thx – emcee22 Dec 22 '20 at 23:04

score 3 · Answer 10 · answered Jan 12 '22 at 14:31

3

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

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

answered Jan 12 '22 at 14:31

Konrad Grzyb

843
10
10

score 1 · Answer 11 · answered Oct 07 '21 at 15:46

1

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.

answered Oct 07 '21 at 15:46

yancaico

989
8
16

score 0 · Answer 12 · answered Sep 09 '19 at 18:50

0

Changing "React" to "react" worked for me.

Incorrect:

import React from "React";

Correct:

import React from "react";

answered Sep 09 '19 at 18:50

Shafqat

1,086
1
11
16

score 0 · Answer 13 · edited Jun 16 '21 at 10:56

0

Writing the import again worked for me.

edited Jun 16 '21 at 10:56

Lim

661
13
28

answered Jan 29 '21 at 22:43

Marco Mesen

492
4
9

score 0 · Answer 14 · answered Jun 25 '21 at 15:31

0

Remove .vue extension and it worked

answered Jun 25 '21 at 15:31

Ahkmy990

87
5

score 0 · Answer 15 · answered Aug 08 '21 at 00:22

If nothing works try:

Remove node_modules
Restart Vetur
yarn or npm i again to get your node_modules
Restart developer window

Renaming files or restarting didn't help. The error started after renaming a file and letting Vetur do it's thing with imports.

Peter · Answer 16 · 2022-03-19T11:17:24.493

0

In my case, I am using Nextjs. Removing the .next folder and starting the app again solved the problem.

Update: The error occurred again. This time deleting .next didn't help. Turned out it was due to a circular dependency in my code.

edited Mar 19 '22 at 11:17

answered Jan 13 '22 at 07:51

Peter

540
5
12

score 0 · Answer 17 · answered May 20 '22 at 15:20

0

For me the problem only went away:

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

answered May 20 '22 at 15:20

Ruvan Fernando

26
7

score -2 · Accepted Answer · answered Jul 06 '18 at 15:08

-2

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

answered Jul 06 '18 at 15:08

zuddsy

1,367
2
9
19

9

what is tisfy ? – kkost Sep 08 '18 at 23:36
6

Updating what? please provide more info on what you updated – katwekibs Jan 19 '20 at 11:06

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

18 Answers18

UPDATE 2021

First

Second

Linked