Naming collision: flux/node_modules/fbjs/flow/include/ErrorUtils.js

[davidLeonardi]

Hello,

After upgrading to 0.18.0 and rebuilding my project from scratch (Deleting all files, generating a new project via react-native init, redowloading only source from version control, recreating the node_modules folder from scratch) i get this:

Error building DependencyGraph:
Error: Naming collision detected: /Users/d/Desktop/project/node_modules/flux/node_modules/fbjs/flow/include/ErrorUtils.js collides with /Users/d/Desktop/project/node_modules/react-native/Libraries/Utilities/ErrorUtils.js

My environment:
npm 3.5.1
node v4.1.1
lastest react-native-cli tools
OSX

My package.json's dependencies:
"fbemitter": "^2.0.0",
"flux": "^2.1.1",
"react-native": "0.18.0",
"react-native-swipeout": "^2.0.11",
"react-mixin": "^3.0.0",
"gb-native-router": "^0.6.0",
"react-native-item-cell": "^1.3.0",
"react-native-linear-gradient": "v1.3.0"

[facebook-github-bot]

Hey sethx, 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!

[chirag04]

@SEthX npm3 is not officially recommended yet. Till then can you try removing fbjs from any nested dep and installing it under ./node_modules/fbjs

Here are few steps for anyone else having the same problem:

1. rm -rf node_modules
2. npm install
3. npm install fbjs
4. find . -name 'fbjs' -print
5. manually remove all fbjs inside any node_module except one at top level
6. rm -fr $TMPDIR/react-*
7. watchman watch-del-all
8. npm start --reset-cache

[lesniakania]

I had similar issue, for me helped upgrading to Node 5.0.2 and npm 3.3.12

[jasonmerino]

I had a similar issue with naming collisions in fbjs, but in different files. The steps that @chirag04 posted fixed it for me.

[adriansdev]

I had a fbjs camelize.js clash but the @chirag04 instructions plus restarting xcode and the iOS simulator to completely clear caches

[dabit3]

@chirag04 fix worked for me as well, thanks!

[sampurcell93]

This fix worked great, thank you.

[joewood]

The fix didn't work for me. The fbjs in npm is different to the ones used by react-native. The version of lib/invariant.js in the package now doesn't have providesModule invariant - this is causing build failures. If you install fbjs@0.6.0 this solves the issue.

[alex-mcleod]

As an extension to the answer by @chirag04, you can add a npm post install script with this line to automatically take care of the problem whenever npm install is run:

find ./node_modules -name "fbjs" -type d -prune -exec sh -c 'if [ {} != "./node_modules/fbjs" ]; then rm -rf {};fi' \;

[joewood]

I found it easier to just tell the packager to ignore all versions of fbjs other than the one you install. So, install your version of fbjs (I found v.0.6 to only work):

npm install fbjs@0.6.0

And then create a rn-cli.config.js file in your root. This worked for me:

var blacklist= require("react-native/packager/blacklist");
var config = {
    getBlacklistRE(platform) {
        return blacklist(platform,[/MYAPPNAME.+\/node_modules\/fbjs.*/]);
    }
}
module.exports = config;

Replacing MYAPPNAME with your app's directory name (remember to escape out any regex chars, like-). All this is doing is adding to the package blacklist regex pattern. The .+ ensures that there must be more than one character between the root dir and the node_modules.

[jihopark]

@joewood's solution worked for me. thanks!