chore(deps): update react monorepo to v16 - autoclosed #630
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This Pull Request renovates the package group "react monorepo" with the following modifications:
Note: This PR was created on a configured schedule ("before 5am on Monday" in timezone
Europe/Paris) and will not receive updates outside those times.react-test-renderer(homepage, source) fromv15.6.2tov16.4.2react-dom(homepage, source) fromv15.6.2tov16.4.2react(homepage, source) fromv15.6.2tov16.4.2Release Notes
facebook/react
v16.4.2Compare Source
React DOM Server
Fix a potential XSS vulnerability when the attacker controls an attribute name (
CVE-2018-6341). This fix is available in the latestreact-dom@​16.4.2, as well as in previous affected minor versions:react-dom@​16.0.1,react-dom@​16.1.2,react-dom@​16.2.1, andreact-dom@​16.3.3. (@gaearon in #13302)Fix a crash in the server renderer when an attribute is called
hasOwnProperty. This fix is only available inreact-dom@​16.4.2. (@gaearon in #13303)v16.4.1Compare Source
React
propTypesto components returned byReact.ForwardRef. (@bvaughn in #12911)React DOM
typechanges from some other types totext. (@spirosikmd in #12135)event.targetvalue for theonChangeevent in IE9. (@nhunzaker in #12976)<React.Fragment />from a component. (@philipp-spiess in #12966)React DOM Server
React Test Renderer
getDerivedStateFromProps()in the shallow renderer to not discard the pending state. (@fatfisz in #13030)v16.4.0Compare Source
React
React.unstable_Profilercomponent for measuring performance. (@bvaughn in #12745)React DOM
getDerivedStateFromProps()regardless of the reason for re-rendering. (@acdlite in #12600 and #12802)forwardRef()on a deepersetState(). (@gaearon in #12690)propTypeson a context provider component. (@nicolevy in #12658)react-lifecycles-compatin<StrictMode>. (@bvaughn in #12644)forwardRef()render function haspropTypesordefaultProps. (@bvaughn in #12644)forwardRef()and context consumers are displayed in the component stack. (@sophiebits in #12777)React Test Renderer
getDerivedStateFromProps()support to match the new React DOM behavior. (@koba04 in #12676)testInstance.parentcrash when the parent is a fragment or another special node. (@gaearon in #12813)forwardRef()components are now discoverable by the test renderer traversal methods. (@gaearon in #12725)setState()updaters that returnnullorundefined. (@koba04 in #12756)React ART
React Call Return (Experimental)
React Reconciler (Experimental)
v16.3.2Compare Source
React
nullorundefinedtoReact.cloneElement. (@nicolevy in #12534)React DOM
<StrictMode>. (@bvaughn in #12546)unstable_observedBitsAPI with nesting. (@gaearon in #12543)React Test Renderer
v16.3.1Compare Source
React
Fragment. (@heikkilamarko in #12504)setState()in constructor. (@gaearon in #12532)React DOM
getDerivedStateFromProps()not getting applied in some cases. (@acdlite in #12528)Create Subscription
v16.3.0Compare Source
React
React.createRef()API as an ergonomic alternative to callback refs. (@trueadm in #12162)React.forwardRef()API to let components forward their refs to a child. (@bvaughn in #12346)React.Fragment. (@XaveScor in #11823)React.unstable_AsyncComponentwithReact.unstable_AsyncMode. (@acdlite in #12117)setState()on an unmounted component. (@sophiebits in #12347)React DOM
getDerivedStateFromProps()lifecycle andUNSAFE_aliases for the legacy lifecycles. (@bvaughn in #12028)getSnapshotBeforeUpdate()lifecycle. (@bvaughn in #12404)<React.StrictMode>wrapper to help prepare apps for async rendering. (@bvaughn in #12083)onLoadandonErrorevents on the<link>tag. (@roderickhsiao in #11825)noModuleboolean attribute on the<script>tag. (@aweary in #11900)onKeyPressin more browsers. (@nstraub in #10514)valueanddefaultValueto ignore Symbol values. (@nhunzaker in #11741)operawith anullvalue. @alisherdavronov in #11854)<option selected>. (@watadarkstar in #11821)ReactDOM.unstable_createPortal()in favor ofReactDOM.createPortal(). (@prometheansacrifice in #11747)React DOM Server
React.Component. (@wyze in #11993)this.stateof different components getting mixed up. (@sophiebits in #12323)v16.2.0Compare Source
React
Fragmentas named export to React. (@clemmy in #10783)React.Childrenutilities. (@MatteoVH in #11422)React DOM
onChangeevent in some cases. (@jquense in #11028)React Test Renderer
setState()callback firing too early when called fromcomponentWillMount. (@accordeiro in #11507)React Reconciler
react-reconciler/reflectionwith utilities useful to custom renderers. (@rivenhk in #11683)Internal Changes
v16.1.1Compare Source
React
React DOM
captureattribute. (@maxschmeling in #11424)React DOM Server
ReactDOMServerpublic API. (@travi in #11531)autoFocus={false}attribute on the server. (@gaearon in #11543)React Reconciler
v16.1.0Compare Source
Discontinuing Bower Releases
Starting with 16.1.0, we will no longer be publishing new releases on Bower. You can continue using Bower for old releases, or point your Bower configs to the React UMD builds hosted on unpkg that mirror npm releases and will continue to be updated.
All Packages
React
React.Childrenutilities. (@MatteoVH in #11378)rendermethod but doesn't extend a known base class. (@sw-yx in #11168)React DOM
onas a custom attribute for AMP. (@nuc in #11153)onMouseEnterandonMouseLeavefiring on wrong elements. (@gaearon in #11164)nullshowing up in a warning instead of the component stack. (@gaearon in #10915)tabIndexnot getting applied to SVG elements. (@gaearon in #11034)dangerouslySetInnerHTMLin IE. (@OriR in #11108)form.reset()to respectdefaultValueon uncontrolled<select>. (@aweary in #11057)<textarea>placeholder not rendering on IE11. (@gaearon in #11177)<dialog>element. (@gaearon in #11035)componentDidReceivePropsmethod. (@iamtommcc in #11479)contentEditableandchildren. (@Ethan-Arrowood in #11208)selectgets nullvalue. (@Hendeca in #11141)React DOM Server
suppressHydrationWarningattribute for intentional client/server text mismatches. (@sebmarkbage in #11126)autoFocusattribute into SSR markup. (@gaearon in #11192)React Test Renderer and Test Utils
setState()calls incomponentWillMount()in shallow renderer. (@Hypnosphi in #11167)shouldComponentUpdate()afterforceUpdate(). (@d4rky-pl in #11239 and #11439)forceUpdate()andReact.PureComponentcorrectly. (@koba04 in #11440)package.jsondependency. (@gaearon in #11340)React ART
package.jsondependency. (@gaearon in #11341)react-art/Circle,react-art/Rectangle, andreact-art/Wedge. (@gaearon in #11343)React Reconciler (Experimental)
React Call Return (Experimental)
v16.0.0Compare Source
New JS Environment Requirements
New Features
render. (Docs coming soon!)ReactDOM.createPortal(). (Docs coming soon!)ReactDOMServer.renderToNodeStream()andReactDOMServer.renderToStaticNodeStream(). (@aickin in #10425, #10044, #10039, #10024, #9264, and others.)Breaking Changes
There are several changes to the behavior of scheduling and lifecycle methods:
ReactDOM.render()andReactDOM.unstable_renderIntoContainer()now returnnullif called from inside a lifecycle method.setStatebehavior:setStatewith null no longer triggers an update. This allows you to decide in an updater function if you want to re-render.setStatedirectly in render always causes an update. This was not previously the case. Regardless, you should not be callingsetStatefrom render.setStatecallback (second argument) now fires immediately aftercomponentDidMount/componentDidUpdateinstead of after all components have rendered.<A />with<B />,B.componentWillMountnow always happens beforeA.componentWillUnmount. Previously,A.componentWillUnmountcould fire first in some cases.refto a component would always detach the ref before that component's render is called. Now, we change thereflater, when applying the changes to the DOM.ReactDOM.unmountComponentAtNode. See this example.componentDidUpdatelifecycle no longer receivesprevContextparam. (@bvaughn in #8631)componentDidUpdate()because DOM refs are not available. This also makes it consistent withcomponentDidMount()(which does not get called in previous versions either).unstable_batchedUpdates()anymore.ReactDOM.unstable_batchedUpdatesnow only takes one extra argument after the callback.The names and paths to the single-file browser builds have changed to emphasize the difference between development and production builds. For example:
react/dist/react.js→react/umd/react.development.jsreact/dist/react.min.js→react/umd/react.production.min.jsreact-dom/dist/react-dom.js→react-dom/umd/react-dom.development.jsreact-dom/dist/react-dom.min.js→react-dom/umd/react-dom.production.min.jsThe server renderer has been completely rewritten, with some improvements:
ReactDOM.hydrateinstead ofReactDOM.renderif you're reviving server rendered HTML. Keep usingReactDOM.renderif you're just doing client-side rendering.When "unknown" props are passed to DOM components, for valid values, React will now render them in the DOM. See this post for more details. (@nhunzaker in #10385, 10564, #10495 and others)
Errors in the render and lifecycle methods now unmount the component tree by default. To prevent this, add error boundaries to the appropriate places in the UI.
Removed Deprecations
react-with-addons.jsbuild anymore. All compatible addons are published separately on npm, and have single-file browser versions if you need them.React.createClassis now available as create-react-class,React.PropTypesas prop-types,React.DOMas react-dom-factories, react-addons-test-utils as react-dom/test-utils, and shallow renderer as react-test-renderer/shallow. See 15.5.0 and 15.6.0 blog posts for instructions on migrating code and automated codemods.This PR has been generated by Renovate Bot.