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

Warning "There is another module with a equal name when case is ignored." #382

Closed
byelims opened this issue Jul 29, 2014 · 56 comments
Closed

Comments

@byelims
Copy link

byelims commented Jul 29, 2014

Today when I build my project, webpack warns me a lot like this:

WARNING in .//fluxxor//lodash-node/modern/internals/baseCreate.js
There is another module with a equal name when case is ignored.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Rename module if multiple modules are expected or use equal casing if one module is expected.

WARNING in .//Fluxxor//lodash-node/modern/internals/baseCreate.js
There is another module with a equal name when case is ignored.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Rename module if multiple modules are expected or use equal casing if one module is expected.

It was fine yesterday. I don't know what is wrong. There is only fluxxor in node_modules. I have tried to remove node_modules directory completely and then re-install. But it doesn't help.

I'm on OS X 10.9.4. Any ideas?

@byelims
Copy link
Author

byelims commented Jul 29, 2014

I have found the answer. In a file, I made a typo:

var fluxxor = require('Fluxxor');    //should be require('fluxxor')

The filesystem is case-insensitive, so webpack will compile the same file twice.

@byelims byelims closed this as completed Jul 29, 2014
@delacruz-dev
Copy link

thanks for sharing! I was having the same issue :) 👍

@brandonaaskov
Copy link

👍 thanks for sharing

@jakoblind
Copy link

Thanks for sharing! Had the same issue!

ravirani added a commit to getcircle/circle-web that referenced this issue Nov 23, 2015
@Vall3y
Copy link

Vall3y commented Dec 13, 2015

+1 👍

@mrblackus
Copy link

👍

1 similar comment
@arcseldon
Copy link

👍

@gitdarin
Copy link

gitdarin commented Jan 5, 2016

awesome. thank you!

@anhhh11
Copy link

anhhh11 commented Jan 6, 2016

👍

2 similar comments
@arcarson
Copy link

arcarson commented Feb 9, 2016

+1

@shenlq
Copy link

shenlq commented Feb 18, 2016

+1

@shenlq
Copy link

shenlq commented Feb 18, 2016

叼叼叼

@terry-fei
Copy link

👍

@Pradeep-Kumar-S-M
Copy link

I had the same issue. Thank you.

@robatron
Copy link

robatron commented Mar 9, 2016

👍

@dazziola
Copy link

+1 Thanks!

1 similar comment
@Axighi
Copy link

Axighi commented Apr 1, 2016

+1 Thanks!

@PeteDuncanson
Copy link

quick search through all my files for each version of the file it reports but in lowercase (it was reporting it in a file as Uppercase found the two references where I'd got the wrong case. Luckily I'm on windows (although some of you will laugh at the lucky part) so its not case sensitive but I wanted the warning message to disappear :)

Example:

Filename is actually: Price.jsx

searched for: price.jsx to find the references it was complaining about.

@Dhaval8087
Copy link

Thank you so much

@olegdeezus
Copy link

Thanks! That was useful!

@wb-yangxing
Copy link

nice sharing

@EmrysMyrddin
Copy link

This warning should be very much explicit for a simple problem like that. It lacks the file where the problem have been found...

@ghoshabhi
Copy link

Useful info! 👍

@fristys
Copy link

fristys commented Aug 2, 2016

Thanks for the help, this fixed my problem...after a lot of searching. This warning message should be a lot smarter and should actually point to the problematic line in question, enough with this guessing wizardry shit...

@sudkumar
Copy link

(y) Had the same issue. Thanks.

@ahmad2smile
Copy link

ty!!

@StokeMasterJack
Copy link

I had this warning also. It took me two hours to find it. I am on a Mac. What I did, was delete the module in question. Empty my trash. Re-create the module from scratch.

Then I ran flow, which took me straight to the actual error.

Before this "delete the file and empty the trash" exercise, Flow was not reporting the bug. Only webpack was reporting the error. But webpack's error was not helpful.

So it sounds like some kind of file system issue?

@xzjcool
Copy link

xzjcool commented Nov 24, 2016

Thank you +1

@adamkdean
Copy link

Having this too but no way of knowing where the issue is. No changes but now it starts spitting this out? Perhaps it is some sort of FS issue.

@zhangolve
Copy link

oh,help me a lot ,thank you.

@saman
Copy link

saman commented Jan 8, 2017

 Thanks for sharing.

@chvin
Copy link

chvin commented Jan 8, 2017

Thanks for sharing.

@littlelake
Copy link

ty!

@jjtfsalgado
Copy link

thanks ;)

@andrewpurcell
Copy link

👍

@xavibonell
Copy link

thanks, same issue here

@y-lakhdar
Copy link

👍

@pyotruk
Copy link

pyotruk commented Feb 22, 2017

👍 the same issue

@1003865572
Copy link

1003865572 commented Mar 9, 2017

文件夹名为 fluxxor
进入的 时候 却以 Fluxxor 引入,
var fluxxor = require('Fluxxor'); //should be require('fluxxor')

大小写不一造成的,
(英文看不懂,我翻译了 上面那哥们儿的回复)

@JackDan9
Copy link

JackDan9 commented Apr 21, 2017

problem(Error case):
WARNING in ./components/common/NoData.jsx
There is another module with an equal name when case is ignored.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Rename module if multiple modules are expected or use equal casing if one module is expected.
Answer:
It is a kind of Warning, Remind us of right writing(case-semantic).
Answer(Right case):
./component/Common/NoData.jsx.

@chengkj99
Copy link

@byelims just this error, thank you !

@iamalvisng
Copy link

Thank you so much for sharing.

In my case, I did

import React from 'React';

:(

@mohitbhatia1994
Copy link

mohitbhatia1994 commented Aug 3, 2017

@byelims Thanks a lot for sharing.

@cunjieliu
Copy link

Good! Thanks for sharing!

@cemarguvanli
Copy link

thanks for sharing!

@G1anpierre
Copy link

Thanks for sharing! have had the same issue! haha

@melkishengue
Copy link

👍cool, thanks

@shanghaiese
Copy link

Thanks !!!

@ZenBerry
Copy link

Wonderful) Many thanks. Have a lovely day! ^_^

antonparussimov added a commit to antonparussimov/vue-flatpicker that referenced this issue Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests