facebook/react Shipping Report

Built-in React Native components (e.g. View) currently trigger deprecation warnings for lifecycles componentWillMount and componentWillReceiveProps due to these DEV-only mixins added by the NativeMethodsMixin component.

Long term, we should remove the deprecated lifecycles but for the time being, I think we should just suppress the warnings from the builtin methods specifically using a similar technique as the react-lifecycles-compat polyfill. This will hopefully improve the in-between period for the RN community significantly.

Thanks for https://github.com/facebook/react/pull/12210 @gaearon - I'd been running mostly in the dark and faking data, now have an easy PR to test against!

The main change is:

-        Math.abs(r.prevFileSizeChange) > percentToWarrentShowing ||
-        Math.abs(r.prevGzipSizeChange) > percentToWarrentShowing
+        Math.abs(r.prevFileSizeChange) >= percentToWarrentShowing ||
+        Math.abs(r.prevGzipSizeChange) >= percentToWarrentShowing

It means that a 1% change will show 👍

Which means it'll get picked up and shown. The other changes are to loosen up the constraint on highlighting when either react or react-dom changes outside of the closed table.

When I run yarn danger pr https://github.com/facebook/react/pull/12210 (after checking out the branch, and running yarn build to get the right results.json), the output by Danger is this:

ReactDOM: size +1%, gzip: +1% -

This shim needs to be in GitHub, or syncing will wipe it out and cause fbsource breakage.

Noticed the release script didn't handle this case when trying to publish an alpha containing the new react-is package.

• branch specifies a branch other than master
• local skips pulling from the remote branch and checking CircleCI
• tag specifies an npm dist tag other than latest or next

We may add a higher-level canary option in the future.

Test plan: I used this to publish 16.4.0-alpha.7926752 and it worked.

Re: https://github.com/facebook/react/pull/12220#issuecomment-365617693

Uses the Danger DSL to grab the base repo and branch, adds it as a remote (and fetches) for reference master on my personal fork is at d906de7 and master for facebook/react is 1fd205a (as of creating this PR)

I think it would be nice to add a test to verity that React.Fragment works fine with ShallowRenderer.

Pushing an early version of this for testing and demonstration purposes.

Adds support for ContextProvider, ContextConsumer, and Mode.

Closes https://github.com/facebook/react/issues/12150