-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
Comments
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. |
thanks for sharing! I was having the same issue :) 👍 |
👍 thanks for sharing |
Thanks for sharing! Had the same issue! |
See these for more info: protobufjs/protobuf.js@1216ca8 webpack/webpack#382 protobufjs/protobuf.js#339
+1 👍 |
👍 |
1 similar comment
👍 |
awesome. thank you! |
👍 |
2 similar comments
+1 |
+1 |
叼叼叼 |
👍 |
I had the same issue. Thank you. |
👍 |
+1 Thanks! |
1 similar comment
+1 Thanks! |
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. |
Thank you so much |
Thanks! That was useful! |
nice sharing |
This warning should be very much explicit for a simple problem like that. It lacks the file where the problem have been found... |
Useful info! 👍 |
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... |
(y) Had the same issue. Thanks. |
ty!! |
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? |
Thank you +1 |
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. |
oh,help me a lot ,thank you. |
Thanks for sharing. |
Thanks for sharing. |
ty! |
thanks ;) |
👍 |
thanks, same issue here |
👍 |
👍 the same issue |
文件夹名为 fluxxor 大小写不一造成的, |
problem(Error case): |
@byelims just this error, thank you ! |
Thank you so much for sharing. In my case, I did import React from 'React'; :( |
@byelims Thanks a lot for sharing. |
Good! Thanks for sharing! |
thanks for sharing! |
Thanks for sharing! have had the same issue! haha |
👍cool, thanks |
Thanks !!! |
Wonderful) Many thanks. Have a lovely day! ^_^ |
Today when I build my project, webpack warns me a lot like this:
It was fine yesterday. I don't know what is wrong. There is only
fluxxor
innode_modules
. I have tried to removenode_modules
directory completely and then re-install. But it doesn't help.I'm on OS X 10.9.4. Any ideas?
The text was updated successfully, but these errors were encountered: