react-native: [0.18] Error: Naming collision detected

Hi there, I just updated my RN package to 0.18, and then I ran a react-native upgrade. However, there seems to be a problem starting the packager:

Error building DependencyGraph:
 Error: Naming collision detected: /Users/samuelpurcell/Projects/Cymbal-Android/node_modules/fbjs/flow/include/warning.js collides with /Users/samuelpurcell/Projects/Cymbal-Android/node_modules/fbjs/lib/warning.js
    at HasteMap._updateHasteMap (HasteMap.js:132:13)
    at HasteMap.js:103:28
    at tryCallOne (/Users/samuelpurcell/Projects/Cymbal-Android/node_modules/promise/lib/core.js:37:12)
    at /Users/samuelpurcell/Projects/Cymbal-Android/node_modules/promise/lib/core.js:123:15
    at flush (/Users/samuelpurcell/Projects/Cymbal-Android/node_modules/asap/raw.js:50:29)
    at nextTickCallbackWith0Args (node.js:456:9)
    at process._tickCallback (node.js:385:13)

I have tried fixing problems with the watchman cache, using the --reset-cache option, and the rm -rf $TMPDIR/react-packager-* method. Additionally, I have looked into this specific error, but I can only find examples where it is the result of a collision between and extra node_modules/react-native/node_modules directory and others… this seems to be a more fundamental problem. Any advice would be appreciated.

Running node 5.4.0 and npm 3.3.12.

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 37 (15 by maintainers)

Most upvoted comments

As of the upcoming 0.22.0 release, React Native depends on both react and fbjs via npm, which should solve the duplicate dependency issues. Please give 0.22.0-rc a try!

We’re closing out this issue - feel free to continue discussion, or reopen should this error persist on the latest versions of React Native.

jsierles on Mar 20, 2016