Brian Vaughn d3b183c323 Debug render-phase side effects in "strict" mode (#12094) ... A new feature flag has been added, debugRenderPhaseSideEffectsForStrictMode. When enabled, StrictMode subtrees will also double-invoke lifecycles in the same way as debugRenderPhaseSideEffects. By default, this flag is enabled for __DEV__ only. Internally we can toggle it with a GK. This breaks several of our incremental tests which make use of the noop-renderer. Updating the tests to account for the double-rendering in development mode makes them significantly more complicated. The most straight forward fix for this will be to convert them to be run as internal tests only. I believe this is reasonable since we are the only people making use of the noop renderer.		2018-01-25 14:30:53 -08:00
..
ReactFeatureFlags.native-fabric.js	Debug render-phase side effects in "strict" mode (#12094)	2018-01-25 14:30:53 -08:00
ReactFeatureFlags.native.js	Debug render-phase side effects in "strict" mode (#12094)	2018-01-25 14:30:53 -08:00
ReactFeatureFlags.www.js	Debug render-phase side effects in "strict" mode (#12094)	2018-01-25 14:30:53 -08:00
invokeGuardedCallback.www.js	Use static injection for ReactErrorUtils (#11725)	2017-11-30 19:10:46 +00:00
lowPriorityWarning.www.js	Unify the way we fork modules (#11711)	2017-11-30 12:11:00 +00:00
object-assign.umd.js	Unify the way we fork modules (#11711)	2017-11-30 12:11:00 +00:00