GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
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
Trying out React 16 Beta
It works, but I don't think this is merge ready yet.
Mostly we've fallen behind the react train. I've updated PropTypes and CreateClass to their shims but if this moved to ES6 Modules and JSX that would help quite a bit further.
Trying out react@next
Curious: what is the necessity for these aliases?
Looks like it's forcing UMD instead of default (CJS) target?
Right. I’m curious why. In the past people used to do this to speed up DEV builds (since React had too many modules). But now CJS is also a single bundle so maybe it‘s unnecessary.
Yeah, sorry. I wasn't really trying to answer your question so much as confirming that I understood what it was doing.
Your assertion seems legit.
@jasonLaster is the right person to answer that question, my understanding is that this has to do with how we package react within the browser toolbox.
Here was the warning we saw:
And the fix:
We've had several other issues creep in over time
So the issue is due to a custom module system (per #23)? I'm not sure what “single module plugin” is.
I guess if it works around a bug for you, that’s cool, I just wanted to verify. Please not react.development bundle is not suitable for production.
Closing this out for now, its a good start but will take some more work to make it happen. 🙇