-
Notifications
You must be signed in to change notification settings - Fork 754
Addons not being loaded to global state #447
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
Comments
Yep, it's intentional that they're exposed on I'd also love to see a more flexible & powerful way to load those things. You can see the existing build setup here: https://github.com/reactjs/react-rails/tree/master/react-builds. The addons object is created in I think it'd be nice to pick-and-choose your addons with |
You can get them from Hope that helps! |
Thanks @davidlormor for the question and @rmosolgo for the clarification! Just to be clear for anyone else running across this problem. You'll need
I couldn't get a-la-carte to work either. c18aa38 |
This appears to be a similar issue to #315. Configuration and everything was set up correctly just like the previous issue, but when trying to use
ReactCSSTransitionGroup
in a component (defined inapp/assets/javascripts/admin/components
) I get a the following error in the browser console:Uncaught ReferenceError: ReactCSSTransitionGroup is not defined
I can find the "development_with_addons" react file being loaded, but apparently the addon components being defined in this file are not being loaded to the global state for other components to use.
Adding
var ReactCSSTransitionGroup = React.addons.CSSTransitionGroup;
to application.js resolves the issue. Just wonder if there's a cleaner/more automated way to ensure that all components are being required on load?The text was updated successfully, but these errors were encountered: