-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pre-release 0.8.0, problem with the context #608
Comments
Hi @oliviertassinari, I have a couple of questions that can help me get an idea of what's happening:
One thing we've noticed is having multiple versions of react in your |
Oh, indeed, I have two versions of React. I will try with only one. Using |
I confirm, I solved the problem by using only one version of React. thanks @mmrtnz |
For other people looking for a solution: with webpack you can force all libraries to use the same version of React by setting up an alias. See this blog: http://www.justincarmony.com/blog/2015/04/02/webpack-react-multiple-versions-issues/ Add this to your module.exports = {
// ... other settings ...
resolve: {
// ...other resolve settings ...
alias: {
"react": __dirname + '/node_modules/react',
"react/addons": __dirname + '/node_modules/react/addons',
}
}
// ... other settings ...
} |
@oliviertassinari How do you set only one React version? Now I'm using webpack and react version is 0.1.3.3. |
@xushao0305 I had one react directory at the first level of node_modules and a second one at the level of material-ui. I removed the second one. |
@oliviertassinari Fine! It works after I remove the React directory of material-ui. Thanks. |
The react folder appears inside material-ui if you run |
@oliviertassinari OK. thanks olivier |
I'm struggling to migrate to the new version.
The context is undefined in a lot of components (this.context), not every one. Any idea why ?
I'm using React 0.13.2 and Webpack to build my application.
And, shounldn't we use isRequired?
The text was updated successfully, but these errors were encountered: