question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Webpack warning: There is another module with an equal name when case is ignored

See original GitHub issue

I’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:closed
  • Created 7 years ago
  • Comments:16 (11 by maintainers)

github_iconTop GitHub Comments

2reactions
jemgravescommented, Apr 23, 2017

I was able to reproduce with the following steps:

  1. On a Windows machine, create a new directory ‘TEST’. (Doesn’t matter what you name it, just put in caps somewhere).
  2. In your CLI navigate to your directory and create-react-app app-test within it.
  3. npm start
  4. Terminate the development server
  5. In some other window, without closing your currently open CLI (explorer, another CLI environment), rename ‘TEST’ to ‘test’. (Change the case to its opposite case, whatever you named it).
  6. Return to your original CLI and run 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 running npm start. Not sure what could cause it to happen consistently, but it might be related to some file structure changes during development.

0reactions
gaearoncommented, May 3, 2017

@Urthen Thanks for taking a look!

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found