errors whe trying the example

[storybook-eol]

errors whe trying the example

[alexcurtis]

@Bramas Hi. It might be that you have 2 react libs in your dependency tree. I've made react a dev dependency, to avoid this issue though. Could you check your project and make sure you don't have more that one version of react installed please

[alexcurtis]

@Bramas It might be work running npm dedupe first to see if that solves the issue: https://docs.npmjs.com/cli/dedupe

[Bramas]

Thanks for your help.

First I removed reactify (which is deprecated) to use babel. Here is my package.json:

{
    //... name and desc
  "scripts": {
    "start": "browserify -t [ babelify --presets [ es2015 react ] ] -t debowerify ./index.js > ./bundle.js"
  },
  "devDependencies": {
    "babel-preset-es2015": "^6.1.18",
    "babel-preset-react": "^6.1.18",
    "babelify": "^7.2.0",
    "react-addons-test-utils": "^0.14.3",
    "react": "^0.14.3",
    "react-dom": "^0.14.3",
    "browserify": "*",
    "debowerify": "*",
    "react-treebeard": "*"
  }
}

But I still get the error.

@alexcurtis I tried to run dedupe but it returns nothing.

I will try to reduce even more my project (which is quite already small) to isolate the problem (because here debowerify can be the reason maybe)

[Bramas]

I removed debowerify.
And index.js only contains exactly the example in the readme.

Same error

[Bramas]

I forgot to mention:
npm version: 2.14.7
node version: 4.2.2

[alexcurtis]

After a quick Google. It might be a well known issue with browserify. The suggested fix is to use the browserify-resolutions plugin to dedupe react at the browserify level. Could you give that a quick go to see if it removes the errors. If not, I'll dig a little deeper into my project package and see if its my end. https://www.npmjs.com/package/browserify-resolutions

[alexcurtis]

@Bramas. Would it be possible for you to repo this project into github so I can try to fix it?

[Bramas]

I removed react-treebeard and reinstalled it and it works!

I don't know exactly what caused the problem. I mean it surely comes from conflicting instance of react as you said but where do they come from, i don't know (but certainly not from treebeard!!)

Thanks again for your help and for the great project, now I can have fun with it!!

[alexcurtis]

@Bramas Awesome. I thought it would be something like that. Thanks for the support! If you have any ideas / fixes / improvements, please let me know and i'll try and make it happen. Or, if you wanted to contribute a pull request, that would also be pretty cool!

[bkniffler]

I had similar issues, react-treebeard only showing the symptoms, not being the cause. Double and triple check for duplicate react instances.

[alexcurtis]

@bkniffler I'm struggling to replicate this here. Do you have a small test project that errors that I can see?

[bkniffler]

Oh, sorry, I wasn't clear. I wanted to confirm the previous comments and suggest that everyone who sees this issue should double check for duplicate react instances within their own project!

[alexcurtis]

@bkniffler Ah ok cool. :-)

[dan3721]

Upgrading NPM to 3.10.8 via npm install -g npm resolved the issue for me.