-
Notifications
You must be signed in to change notification settings - Fork 53
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
Component breaks in React 0.13.x #25
Comments
FYI: facebook/react#2661 |
Looks like this was fixed in 590f6d4#diff-69684a9e505635d4c0f1c87dc55ced25 and then reverted again in 0b235ea#diff-69684a9e505635d4c0f1c87dc55ced25 |
I'm using react v0.13.3 The weird thing is that it only throws an error if I use components from a different file. The following code throws the error mentioned at the top of this thread. // Main.jsx
import React from 'react/addons';
import SomeComponent from './SomeComponent.jsx';
export default React.createClass({
render() {
return (
<SomeComponent />
);
}
});
// SomeComponent.jsx
import React from 'react';
export default React.createClass({
render() {
return (
<div></div>
);
}
}); While this code works fine. import React from 'react/addons';
var SomeComponent = React.createClass({
render() {
return (
<div></div>
);
}
});
export default React.createClass({
render() {
return (
<SomeComponent />
);
}
}); |
I solved my problem. I was importing the component from a file that only used |
Interesting. I only use the |
I am getting the problem, and I am not using |
I'm having the same issue using 0.13.3, any updates on how to fix this? |
Same problem - solutions? |
I'd love to get this working in React 0.14.x, but don't know what needs to be changed? I'd be happy to help! |
This is still an issue with this module. I tried to use this and it still calls react directly. Happy to help contribute if needed! |
This component is using the legacy API, not
React.createElement
orReact.createFactory
.The text was updated successfully, but these errors were encountered: