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

allow React 16 in core peerDependencies #1660

Merged
merged 1 commit into from
Oct 4, 2017
Merged

allow React 16 in core peerDependencies #1660

merged 1 commit into from
Oct 4, 2017

Conversation

giladgray
Copy link
Contributor

@giladgray giladgray commented Oct 4, 2017

Fixes #866

Changes proposed in this pull request:

Allow React 16 to be installed alongside Blueprint.

This does not guarantee full support for React 16, but I've manually tested locally and all components render without errors. There may still be issues with deeper interaction logic (though I'm optimistic they'll be very rare), so at least this way folks can encounter those bugs and report them!

Note that until we begin work on 2.0, we are not doing any automated testing against React 16 (see #1659). We are also still using (very old) React typings (see #1031).

upgrade support seems free since there were no warnings with latest 15.x release.
@giladgray giladgray requested a review from adidahiya October 4, 2017 20:20
@adidahiya
Copy link
Contributor

:shipit:

@blueprint-bot
Copy link

allow react 16 in core peerDeps

Preview: documentation | table
Coverage: core | datetime

@giladgray giladgray merged commit 5cc8dc6 into master Oct 4, 2017
@giladgray giladgray deleted the gg/react16 branch October 4, 2017 20:32
@cmslewis cmslewis mentioned this pull request Oct 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants