Webpack warning: There is another module with an equal name when case is ignored
See original GitHub issueI’m using 0.4.1
version and I get:
Warning in (webpack)/buildin/module.js
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.
Warning in ./~/react-scripts/~/webpack/buildin/module.js
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.
when I run the app by npm start
Issue Analytics
- State:
- Created 7 years ago
- Comments:16 (11 by maintainers)
Top Results From Across the Web
Warning "There is another module with a equal name when ...
There is another module with a equal name when case is ignored. This can lead to unexpected behavior when compiling on a filesystem...
Read more >Webpack warning - There is another module with an equal ...
I'm facing a similar problem where it's showing a relative path for the first warning and an absolute path for the second. WARNING...
Read more >Webpack: There is another module with an equal name ... - I Love IT
WARNING : There is another module with an equal name when case is ignored. After some googling I got a solution! Check all...
Read more >webpack filename case warnings - purple:ops
js There is another module with a equal name when case is ignored. This can lead to unexpected behavior when compiling on a...
Read more >Output - webpack
If multiple modules would result in the same name, output.devtoolFallbackModuleFilenameTemplate is used instead for these modules.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I was able to reproduce with the following steps:
create-react-app app-test
within it.npm start
npm start
to receive these errors.This happened to me earlier today while I was doing some file cleanup while also developing. I was able to clear them out by
cd..
out back to the root path (just before ‘TEST’) and navigating back in, then runningnpm start
. Not sure what could cause it to happen consistently, but it might be related to some file structure changes during development.@Urthen Thanks for taking a look!