Skip to content
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

Remove react/addons #6285

Merged
merged 1 commit into from
Mar 17, 2016
Merged

Remove react/addons #6285

merged 1 commit into from
Mar 17, 2016

Conversation

gaearon
Copy link
Collaborator

@gaearon gaearon commented Mar 17, 2016

Not sure what the plan is with 15.0 but accessing react/addons in the CommonJS environment has been deprecated since 0.14 betas. This commit removes react/addons entry point.

If the consumer uses CommonJS, they need to switch to using react-addons-<addon name> package as we warned during 0.14. If the consumer uses addons-enabled UMD build, they don’t need to change anything.

Can we get this into v15?

@jimfb
Copy link
Contributor

jimfb commented Mar 17, 2016

As long as this won't break the browser-with-addons builds, I'm good with this. 👍

@zpao manages the building/packaging, so it's worth pinging him for a go ahead.

@gaearon
Copy link
Collaborator Author

gaearon commented Mar 17, 2016

As far as I can see the UMD addons build uses ReactWithAddons which stays. Only the file that contained the warning is removed, and that one was specifically in the npm React package folder and outside the source directory.

@zpao
Copy link
Member

zpao commented Mar 17, 2016

I wish we had remembered to do this before rc but that's ok. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants