Multiple modules with names that only differ in casing (setImmediate)
See original GitHub issueI am running into some really odd behavior with fbjs 0.8.12 and webpack 2. I am getting a warning for setImmediate
referencing the same module name with different casing. It looks like setimmediate
pollyfill is being wrapped by a setImmediate
module. Here is the warning that I am seeing (I’ve removed full paths on the node module references and replaced with ${project-path})
WARNING in ./~/fbjs/lib/setImmediate.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:
* ${project-path}/node_modules/fbjs/lib/setImmediate.js
Used by 1 module(s), i. e.
${project-path}/node_modules/draft-js/lib/editOnBeforeInput.js
* ${project-path}/node_modules/fbjs/lib/setimmediate.js
Used by 2 module(s), i. e.
${project-path}/node_modules/fbjs/lib/setImmediate.js
As soon as I add content to Editor (in draft-js 0.10.0) I am getting an error:
editOnBeforeInput.js?3bad:126 Uncaught TypeError: setImmediate is not a function
at editOnBeforeInput (eval at ./node_modules/draft-js/lib/editOnBeforeInput.js (bundle.js:1512:1), <anonymous>:126:5)
at eval (eval at ./node_modules/draft-js/lib/DraftEditor.react.js (bundle.js:1256:1), <anonymous>:144:19)
at Object.ReactErrorUtils.invokeGuardedCallback (eval at ./node_modules/react-dom/lib/ReactErrorUtils.js (bundle.js:5229:1), <anonymous>:69:16)
at executeDispatch (eval at ./node_modules/react-dom/lib/EventPluginUtils.js (bundle.js:4949:1), <anonymous>:85:21)
at Object.executeDispatchesInOrder (eval at ./node_modules/react-dom/lib/EventPluginUtils.js (bundle.js:4949:1), <anonymous>:108:5)
at executeDispatchesAndRelease (eval at ./node_modules/react-dom/lib/EventPluginHub.js (bundle.js:4933:1), <anonymous>:43:22)
at executeDispatchesAndReleaseTopLevel (eval at ./node_modules/react-dom/lib/EventPluginHub.js (bundle.js:4933:1), <anonymous>:54:10)
at Array.forEach (native)
at forEachAccumulated (eval at ./node_modules/react-dom/lib/forEachAccumulated.js (bundle.js:5645:1), <anonymous>:24:9)
at Object.processEventQueue (eval at ./node_modules/react-dom/lib/EventPluginHub.js (bundle.js:4933:1), <anonymous>:257:7)
It seems to me that the wrapping module name should not match the external library. I’d be glad to open a pull request with a change. Please advise.
Issue Analytics
- State:
- Created 6 years ago
- Comments:27 (4 by maintainers)
Top Results From Across the Web
Webpack: "there are multiple modules with names that only ...
Webpack: "there are multiple modules with names that only differ in casing" but modules referenced are identical - Stack Overflow. Stack ...
Read more >There are multiple modules with names that only differ in casing.
There are multiple modules with names that only differ in casing. This can lead to unexpected behavior when compiling on a filesystem with...
Read more >RESOLVED There are multiple modules with names that ...
There are multiple modules with names that only differ in casing. This can lead to unexpected behavior when compiling on a filesystem with...
Read more >Webpack "there are multiple modules with names that only ...
And of course, the first thing you do is google the error "there are multiple modules with names that only differ in casing"...
Read more >There are multiple modules with names that only differ in casing
Join this channel to get access to perks:https://www.youtube.com/channel/UCoSpmr2KNOxjwE_B9ynUmig/joinMy GearCamera ...
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 FreeTop 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
Top GitHub Comments
This issue still exists in 2022 😃
FYI This fix is to manually edit node_modules/fbjs/lib/setImmediate.js
@jcardoz i had the same caseSensitive issue upon using webpack 2 along with angular 4 , when i mistakenly created two folders one with camelcase and other with dash/hyphen . Thanks to you .!! on removing one folder and merging the contents into single directory resolved the issue!! Thanks again!!