"Naming collision detected" on start

[siuying]

Found a "Naming collision detected" on launch, where a fbjs file is collides with another fbjs files ...

Error building DependencyGraph:
 Error: Naming collision detected: app/node_modules/fbjs/flow/include/CSSCore.js 
 collides with app/node_modules/fbjs/lib/CSSCore.js

react-native -v
react-native-cli: 0.1.8
react-native: 0.18.0-rc

[facebook-github-bot]

Hey siuying, thanks for reporting this issue!

React Native, as you've probably heard, is getting really popular and truth is we're getting a bit overwhelmed by the activity surrounding it. There are just too many issues for us to manage properly.

• If you don't know how to do something or something is not working as you expect but not sure it's a bug, please ask on StackOverflow with the tag react-native or for more real time interactions, ask on Discord in the #react-native channel.
• If this is a feature request or a bug that you would like to be fixed, please report it on Product Pains. It has a ranking feature that lets us focus on the most important issues the community is experiencing.
• We welcome clear issues and PRs that are ready for in-depth discussion. Please provide screenshots where appropriate and always mention the version of React Native you're using. Thank you for your contributions!

[respectTheCode]

I am running into the same problem

[fsp]

I solved this issue by erasing fbjs from react native's node_modules folder.

[corbt]

I ran into this same issue when updating from react-redux 3 to 4. I tried @fsp's solution but it didn't fix it. I ended up blowing up the whole node_modules folder and reinstalling, and then doing what @FSB said, which fixed the issue for me.

I'm using 0.18-rc (but I've switched between 0.18-rc, 0.17 and master a number of times recently, so it's possible my node_modules folder was in a weird/inconsistent state).

[masom]

Happens on rm -rf node_modules && npm install with 0.18.0-rc

Having the exact same issue with the fbjs package. Removing it manually did not fix it for me, because a conflict still exists but then in the node_modules/fbemitter directory.

[rclai]

I am also having this issue and none of the above solutions worked at all, even with npm cache clear:

[10:04:24 PM] <END>   Crawling File System (885ms)
[10:04:24 PM] <START> Building in-memory fs for JavaScript
[10:04:26 PM] <END>   Building in-memory fs for JavaScript (1573ms)
[10:04:26 PM] <START> Building in-memory fs for Assets
[10:04:27 PM] <END>   Building in-memory fs for Assets (1516ms)
[10:04:27 PM] <START> Building Haste Map
[10:04:29 PM] <START> Building (deprecated) Asset Map
[10:04:29 PM] <END>   Building (deprecated) Asset Map (612ms)
Error building DependencyGraph:
 Error: Naming collision detected: /home/rlai/react-projects/Todos/node_modules/react/node_modules/fbjs/lib/UserAgentData.js collides with /home/rlai/react-projects/Todos/node_modules/react-native/node_modules/fbjs/lib/UserAgentData.js
    at HasteMap._updateHasteMap (HasteMap.js:132:13)
    at HasteMap.js:103:28
    at tryCallOne (/home/rlai/react-projects/Todos/node_modules/react-native/node_modules/promise/lib/core.js:37:12)
    at /home/rlai/react-projects/Todos/node_modules/react-native/node_modules/promise/lib/core.js:123:15
    at flush (/home/rlai/react-projects/Todos/node_modules/react-native/node_modules/promise/node_modules/asap/raw.js:50:29)
    at doNTCallback0 (node.js:419:9)
    at process._tickCallback (node.js:348:13)

I had to start from a complete new project.

[adamterlson]

Try upgrading to npm@3. Does it work then (after deleting node_modules and npm installing again)?

[jasonmerino]

I'm also running into a similar naming collision error when trying to upgrade to 0.18.1. Mine shows as follows:

[10:33:06 AM] <END>   Crawling File System (1352ms)
[10:33:06 AM] <START> Building in-memory fs for JavaScript
[10:33:06 AM] <END>   Building in-memory fs for JavaScript (335ms)
[10:33:06 AM] <START> Building in-memory fs for Assets
[10:33:06 AM] <END>   Building in-memory fs for Assets (310ms)
[10:33:06 AM] <START> Building Haste Map
[10:33:07 AM] <START> Building (deprecated) Asset Map
[10:33:07 AM] <END>   Building (deprecated) Asset Map (159ms)
Error building DependencyGraph:
 Error: Naming collision detected: /Users/jason.merino/Code/MyApp/node_modules/fbjs/flow/include/warning.js collides with /Users/jason.merino/Code/MyApp/node_modules/fbemitter/node_modules/fbjs/lib/warning.js
    at HasteMap._updateHasteMap (HasteMap.js:132:13)
    at HasteMap.js:103:28
    at tryCallOne (/Users/jason.merino/Code/MyApp/node_modules/promise/lib/core.js:37:12)
    at /Users/jason.merino/Code/MyApp/node_modules/promise/lib/core.js:123:15
    at flush (/Users/jason.merino/Code/MyApp/node_modules/asap/raw.js:50:29)
    at nextTickCallbackWith0Args (node.js:452:9)
    at process._tickCallback (node.js:381:13)

I have done the following and it still shows up:

rm -rf node_modules
npm cache clean
npm i

Here's my current setup

npm 3.3.12
react native 0.18.1

[corbt]

Ok yeah @jasonmerino probably the version of fbjs that "fbemitter" wants doesn't match the version that react-native requires, so even npm3 installs it twice. This is a problem we need to get solved.

[jasonmerino]

Thanks @corbt! Yeah, I was thinking that was odd that npm3 still had some nested dependencies, but a version mismatch makes sense.

[ferologics]

Same problem here on:
npm 3.3.12
react native 0.18.1

Error: Naming collision detected: /Users/master/Pomodoro/node_modules/reactfire/node_modules/react/lib/BeforeInputEventPlugin.js collides with /Users/master/Pomodoro/node_modules/react/lib/BeforeInputEventPlugin.js

After deleting the BeforeInputEventPlugin from "node_modules/reactfire/" dir I get

Error: Naming collision detected: /Users/master/Pomodoro/node_modules/reactfire/node_modules/react/lib/CSSCore.js collides with /Users/master/Pomodoro/node_modules/fbjs/lib/CSSCore.js

[ericraio]

@fsp thanks! I was able to fix this by removing the fbjs directory. I hope there is a proper solution soon.