react-devtools - npm Package Versions

16.0.1 (August 1, 2018)

React DOM Server

• Fix a potential XSS vulnerability when the attacker controls an attribute name (CVE-2018-6341). This fix is available in the latest react-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, and react-dom@16.3.3. (@gaearon in #13302)

15.3.2 (September 19, 2016)

React

• Remove plain object warning from React.createElement & React.cloneElement. (@spudly in #7724)

React DOM

• Add playsInline to supported HTML attributes. (@reaperhulk in #7519)
• Add as to supported HTML attributes. (@kevinslin in #7582)
• Improve DOM nesting validation warning about whitespace. (@sophiebits in #7515)
• Avoid "Member not found" exception in IE10 when calling preventDefault() in Synthetic Events. (@g-palmer in #7411)
• Fix memory leak in onSelect implementation. (@AgtLucas in #7533)
• Improve robustness of document.documentMode checks to handle Google Tag Manager. (@SchleyB in #7594)
• Add more cases to controlled inputs warning. (@marcin-mazurek in #7544)
• Handle case of popup blockers overriding document.createEvent. (@Andarist in #7621)
• Fix issue with dangerouslySetInnerHTML and SVG in Internet Explorer. (@zpao in #7618)
• Improve handling of Japanese IME on Internet Explorer. (@msmania in #7107)

React Test Renderer

• Support error boundaries. (@millermedeiros in #7558, #7569, #7619)
• Skip null ref warning. (@Aweary in #7658)

React Perf Add-on

• Ensure lifecycle timers are stopped on errors. (@gaearon in #7548)

16.0.0 (September 26, 2017)

New JS Environment Requirements

• React 16 depends on the collection types Map and Set, as well as requestAnimationFrame. If you support older browsers and devices which may not yet provide these natively (e.g. <IE11), you may want to include a polyfill.

New Features

• Components can now return arrays and strings from render. (Docs coming soon!)
• Improved error handling with introduction of "error boundaries". Error boundaries are React components that catch JavaScript errors anywhere in their child component tree, log those errors, and display a fallback UI instead of the component tree that crashed.
• First-class support for declaratively rendering a subtree into another DOM node with ReactDOM.createPortal(). (Docs coming soon!)
• Streaming mode for server side rendering is enabled with ReactDOMServer.renderToNodeStream() and ReactDOMServer.renderToStaticNodeStream(). (@aickin in #10425, #10044, #10039, #10024, #9264, and others.)
• React DOM now allows passing non-standard attributes. (@nhunzaker in #10385, 10564, #10495 and others)

Breaking Changes

• There are several changes to the behavior of scheduling and lifecycle methods:
  • ReactDOM.render() and ReactDOM.unstable_renderIntoContainer() now return null if called from inside a lifecycle method.
    • To work around this, you can either use the new portal API or refs.
  • Minor changes to setState behavior:
    • Calling setState with null no longer triggers an update. This allows you to decide in an updater function if you want to re-render.
    • Calling setState directly in render always causes an update. This was not previously the case. Regardless, you should not be calling setState from render.
    • setState callback (second argument) now fires immediately after componentDidMount / componentDidUpdate instead of after all components have rendered.
  • When replacing <A /> with <B />, B.componentWillMount now always happens before A.componentWillUnmount. Previously, A.componentWillUnmount could fire first in some cases.
  • Previously, changing the ref to a component would always detach the ref before that component's render is called. Now, we change the ref later, when applying the changes to the DOM.
  • It is not safe to re-render into a container that was modified by something other than React. This worked previously in some cases but was never supported. We now emit a warning in this case. Instead you should clean up your component trees using ReactDOM.unmountComponentAtNode. See this example.
  • componentDidUpdate lifecycle no longer receives prevContext param. (@bvaughn in #8631)
  • Non-unique keys may now cause children to be duplicated and/or omitted. Using non-unique keys is not (and has never been) supported, but previously it was a hard error.
  • Shallow renderer no longer calls componentDidUpdate() because DOM refs are not available. This also makes it consistent with componentDidMount() (which does not get called in previous versions either).
  • Shallow renderer does not implement unstable_batchedUpdates() anymore.
  • ReactDOM.unstable_batchedUpdates now 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.js
  • react/dist/react.min.js → react/umd/react.production.min.js
  • react-dom/dist/react-dom.js → react-dom/umd/react-dom.development.js
  • react-dom/dist/react-dom.min.js → react-dom/umd/react-dom.production.min.js

• The server renderer has been completely rewritten, with some improvements:
  • Server rendering does not use markup validation anymore, and instead tries its best to attach to existing DOM, warning about inconsistencies. It also doesn't use comments for empty components and data-reactid attributes on each node anymore.
  • Hydrating a server rendered container now has an explicit API. Use ReactDOM.hydrate instead of ReactDOM.render if you're reviving server rendered HTML. Keep using ReactDOM.render if 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

• There is no react-with-addons.js build anymore. All compatible addons are published separately on npm, and have single-file browser versions if you need them.
• The deprecations introduced in 15.x have been removed from the core package. React.createClass is now available as create-react-class, React.PropTypes as prop-types, React.DOM as 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.

15.3.1 (August 19, 2016)

React

• Improve performance of development builds in various ways. (@gaearon in #7461, #7463, #7483, #7488, #7491, #7510)
• Cleanup internal hooks to improve performance of development builds. (@gaearon in #7464, #7472, #7481, #7496)
• Upgrade fbjs to pick up another performance improvement from @gaearon for development builds. (@zpao in #7532)
• Improve startup time of React in Node. (@zertosh in #7493)
• Improve error message of React.Children.only. (@sophiebits in #7514)

React DOM

• Avoid <input> validation warning from browsers when changing type. (@nhunzaker in #7333)
• Avoid "Member not found" exception in IE10 when calling stopPropagation() in Synthetic Events. (@nhunzaker in #7343)
• Fix issue resulting in inability to update some <input> elements in mobile browsers. (@keyanzhang in #7397)
• Fix memory leak in server rendering. (@keyanzhang in #7410)
• Fix issue resulting in <input type="range"> values not updating when changing min or max. (@troydemonbreun in #7486)
• Add new warning for rare case of attempting to unmount a container owned by a different copy of React. (@ventuno in #7456)

React Test Renderer

• Fix ReactTestInstance::toJSON() with empty top-level components. (@Morhaus in #7523)

React Native Renderer

• Change trackedTouchCount invariant into a console.error for better reliability. (@yungsters in #7400)

15.3.0 (July 29, 2016)

React

• Add React.PureComponent - a new base class to extend, replacing react-addons-pure-render-mixin now that mixins don't work with ES2015 classes. (@sophiebits in #7195)
• Add new warning when modifying this.props.children. (@jimfb in #7001)
• Fixed issue with ref resolution order. (@gaearon in #7101)
• Warn when mixin is undefined. (@swaroopsm in #6158)
• Downgrade "unexpected batch number" invariant to a warning. (@sophiebits in #7133)
• Validate arguments to oneOf and oneOfType PropTypes sooner. (@troydemonbreun in #6316)
• Warn when calling PropTypes directly. (@Aweary in #7132, #7194)
• Improve warning when using Maps as children. (@keyanzhang in #7260)
• Add additional type information to the PropTypes.element warning. (@alexzherdev in #7319)
• Improve component identification in no-op setState warning. (@keyanzhang in #7326)

React DOM

• Fix issue with nested server rendering. (@Aweary in #7033)
• Add xmlns, xmlnsXlink to supported SVG attributes. (@salzhrani in #6471)
• Add referrerPolicy to supported HTML attributes. (@Aweary in #7274)
• Fix issue resulting in <input type="range"> initial value being rounded. (@troydemonbreun in #7251)

React Test Renderer

• Initial public release of package allowing more focused testing. Install with npm install react-test-renderer. (@sophiebits in #6944, #7258, @iamdustan in #7362)

React Perf Add-on

• Fix issue resulting in excessive warnings when encountering an internal measurement error. (@sassanh in #7299)

React TestUtils Add-on

• Implement type property on for events created via TestUtils.Simulate.*. (@yaycmyk in #6154)
• Fix crash when running TestUtils with the production build of React. (@gaearon in #7246)

15.2.0 (July 1, 2016)

React

• Add error codes to production invariants, with links to the view the full error text. (@keyanzhang in #6948)
• Include component stack information in PropType validation warnings. (@troydemonbreun in #6398, @sophiebits in #6771)
• Include component stack information in key warnings. (@keyanzhang in #6799)
• Stop validating props at mount time, only validate at element creation. (@keyanzhang in #6824)
• New invariant providing actionable error in missing instance case. (@yungsters in #6990)
• Add React.PropTypes.symbol to support ES2015 Symbols as props. (@puradox in #6377)
• Fix incorrect coercion of ref or key that are undefined in development (@gaearon in #6880)
• Fix a false positive when passing other element’s props to cloneElement (@ericmatthys in #6268)
• Warn if you attempt to define childContextTypes on a functional component (@Aweary in #6933)

React DOM

• Add warning for unknown properties on DOM elements. (@jimfb in #6800, @gm758 in #7152)
• Properly remove attributes from custom elements. (@grassator in #6748)
• Fix invalid unicode escape in attribute name regular expression. (@nbjahan in #6772)
• Add onLoad handling to <link> element. (@roderickhsiao in #6815)
• Add onError handling to <source> element. (@wadahiro in #6941)
• Handle value and defaultValue more accurately in the DOM. (@jimfb in #6406)
• Fix events issue in environments with mutated Object.prototype. (@Weizenlol in #6886)
• Fix issue where is="null" ended up in the DOM in Firefox. (@darobin in #6896)
• Improved performance of text escaping by using escape-html. (@aickin in #6862)
• Fix issue with dangerouslySetInnerHTML and SVG in Internet Explorer. (@joshhunt in #6982)
• Fix issue with <textarea> placeholders. (@jimfb in #7002)
• Fix controlled vs uncontrolled detection of <input type="radio"/>. (@jimfb in #7003)
• Improve performance of updating text content. (@trueadm in #7005)
• Ensure controlled <select> components behave the same on initial render as they do on updates. (@yiminghe in #5362)

React Perf Add-on

• Add isRunning() API. (@nfcampos in #6763)
• Improve accuracy of lifecycle hook timing. (@gaearon in #6858)
• Fix internal errors when using ReactPerf with portal components. (@gaearon in #6860)
• Fix performance regression. (@sophiebits in #6770)
• Add warning that ReactPerf is not enabled in production. (@sashashakun in #6884)

React CSSTransitionGroup Add-on

• Fix timing issue with null node. (@keyanzhang in #6958)

React Native Renderer

• Dependencies on React Native modules use CommonJS requires instead of providesModule. (@davidaurelio in #6715)

15.1.0 (May 20, 2016)

React

• Ensure we're using the latest object-assign, which has protection against a non-spec-compliant native Object.assign. (@zpao in #6681)
• Add a new warning to communicate that props objects passed to createElement must be plain objects. (@richardscarrott in #6134)
• Fix a batching bug resulting in some lifecycle methods incorrectly being called multiple times. (@sophiebits in #6650)

React DOM

• Fix regression in custom elements support. (@jscissr in #6570)
• Stop incorrectly warning about using onScroll event handler with server rendering. (@Aweary in #6678)
• Fix grammar in the controlled input warning. (@jakeboone02 in #6657)
• Fix issue preventing <object> nodes from being able to read <param> nodes in IE. (@syranide in #6691)
• Fix issue resulting in crash when using experimental error boundaries with server rendering. (@jimfb in #6694)
• Add additional information to the controlled input warning. (@borisyankov in #6341)

React Perf Add-on

• Completely rewritten to collect data more accurately and to be easier to maintain. (@gaearon in #6647, #6046)

React Native Renderer

• Remove some special cases for platform specific branching. (@sebmarkbage in #6660)
• Remove use of merge utility. (@sebmarkbage in #6634)
• Renamed some modules to better indicate usage (@javache in #6643)

15.0.2 (April 29, 2016)

React

• Removed extraneous files from npm package. (@gaearon in #6388)
• Ensure componentWillUnmount is only called once. (@jimfb in #6613)

ReactDOM

• Fixed bug resulting in disabled buttons responding to mouse events in IE. (@nhunzaker in #6215)
• Ensure <option>s are correctly selected when inside <optgroup>. (@trevorsmith in #6442)
• Restore support for rendering into a shadow root. (@Wildhoney in #6462)
• Ensure nested <body> elements are caught when warning for invalid markup. (@keyanzhang in #6469)
• Improve warning when encountering multiple elements with the same key. (@hkal in #6500)

React TestUtils Add-on

• Ensure that functional components do not have an owner. (@gaearon in #6362)
• Handle invalid arguments to scryRenderedDOMComponentsWithClass better. (@ipeters90 in #6529)

React Perf Add-on

• Ignore DOM operations that occur outside the batch operation. (@gaearon in #6516)

React Native Renderer

• These files are now shipped inside the React npm package. They have no impact on React core or ReactDOM.

15.0.0 (April 7, 2016)

Major changes

• Initial render now uses document.createElement instead of generating HTML. Previously we would generate a large string of HTML and then set node.innerHTML. At the time, this was decided to be faster than using document.createElement for the majority of cases and browsers that we supported. Browsers have continued to improve and so overwhelmingly this is no longer true. By using createElement we can make other parts of React faster. (@sophiebits in #5205)
• data-reactid is no longer on every node. As a result of using document.createElement, we can prime the node cache as we create DOM nodes, allowing us to skip a potential lookup (which used the data-reactid attribute). Root nodes will have a data-reactroot attribute and server generated markup will still contain data-reactid. (@sophiebits in #5205)
• No more extra <span>s. ReactDOM will now render plain text nodes interspersed with comment nodes that are used for demarcation. This gives us the same ability to update individual pieces of text, without creating extra nested nodes. If you were targeting these <span>s in your CSS, you will need to adjust accordingly. You can always render them explicitly in your components. (@mwiencek in #5753)
• Rendering null now uses comment nodes. Previously null would render to <noscript> elements. We now use comment nodes. This may cause issues if making use of :nth-child CSS selectors. While we consider this rendering behavior an implementation detail of React, it's worth noting the potential problem. (@sophiebits in #5451)
• Functional components can now return null. We added support for defining stateless components as functions in React 0.14. However, React 0.14 still allowed you to define a class component without extending React.Component or using React.createClass(), so we couldn’t reliably tell if your component is a function or a class, and did not allow returning null from it. This issue is solved in React 15, and you can now return null from any component, whether it is a class or a function. (@jimfb in #5884)
• Improved SVG support. All SVG tags are now fully supported. (Uncommon SVG tags are not present on the React.DOM element helper, but JSX and React.createElement work on all tag names.) All SVG attributes that are implemented by the browsers should be supported too. If you find any attributes that we have missed, please let us know in this issue. (@zpao in #6243)

Breaking changes

• No more extra <span>s.
• React.cloneElement() now resolves defaultProps. We fixed a bug in React.cloneElement() that some components may rely on. If some of the props received by cloneElement() are undefined, it used to return an element with undefined values for those props. We’re changing it to be consistent with createElement(). Now any undefined props passed to cloneElement() are resolved to the corresponding component’s defaultProps. (@truongduy134 in #5997)
• ReactPerf.getLastMeasurements() is opaque. This change won’t affect applications but may break some third-party tools. We are revamping ReactPerf implementation and plan to release it during the 15.x cycle. The internal performance measurement format is subject to change so, for the time being, we consider the return value of ReactPerf.getLastMeasurements() an opaque data structure that should not be relied upon. (@gaearon in #6286)

Removed deprecations

These deprecations were introduced nine months ago in v0.14 with a warning and are removed:

• Deprecated APIs are removed from the React top-level export: findDOMNode, render, renderToString, renderToStaticMarkup, and unmountComponentAtNode. As a reminder, they are now available on ReactDOM and ReactDOMServer. (@jimfb in #5832)
• Deprecated addons are removed: batchedUpdates and cloneWithProps. (@jimfb in #5859, @zpao in #6016)
• Deprecated component instance methods are removed: setProps, replaceProps, and getDOMNode. (@jimfb in #5570)
• Deprecated CommonJS react/addons entry point is removed. As a reminder, you should use separate react-addons-* packages instead. This only applies if you use the CommonJS builds. (@gaearon in #6285)
• Passing children to void elements like <input> was deprecated, and now throws an error. (@jonhester in #3372)
• React-specific properties on DOM refs (e.g. this.refs.div.props) were deprecated, and are removed now. (@jimfb in #5495)

New deprecations, introduced with a warning

Each of these changes will continue to work as before with a new warning until the release of React 16 so you can upgrade your code gradually.

• LinkedStateMixin and valueLink are now deprecated due to very low popularity. If you need this, you can use a wrapper component that implements the same behavior: react-linked-input. (@jimfb in #6127)
• Future versions of React will treat <input value={null}> as a request to clear the input. However, React 0.14 has been ignoring value={null}. React 15 warns you on a null input value and offers you to clarify your intention. To fix the warning, you may explicitly pass an empty string to clear a controlled input, or pass undefined to make the input uncontrolled. (@antoaravinth in #5048)
• ReactPerf.printDOM() was renamed to ReactPerf.printOperations(), and ReactPerf.getMeasurementsSummaryMap() was renamed to ReactPerf.getWasted(). (@gaearon in #6287)

New helpful warnings

• If you use a minified copy of the development build, React DOM kindly encourages you to use the faster production build instead. (@sophiebits in #5083)
• React DOM: When specifying a unit-less CSS value as a string, a future version will not add px automatically. This version now warns in this case (ex: writing style={{width: '300'}}. Unitless number values like width: 300 are unchanged. (@pluma in #5140)
• Synthetic Events will now warn when setting and accessing properties (which will not get cleared appropriately), as well as warn on access after an event has been returned to the pool. (@kentcdodds in #5940 and @koba04 in #5947)
• Elements will now warn when attempting to read ref and key from the props. (@prometheansacrifice in #5744)
• React will now warn if you pass a different props object to super() in the constructor. (@prometheansacrifice in #5346)
• React will now warn if you call setState() inside getChildContext(). (@raineroviir in #6121)
• React DOM now attempts to warn for mistyped event handlers on DOM elements, such as onclick which should be onClick. (@ali in #5361)
• React DOM now warns about NaN values in style. (@jontewks in #5811)
• React DOM now warns if you specify both value and defaultValue for an input. (@mgmcdermott in #5823)
• React DOM now warns if an input switches between being controlled and uncontrolled. (@TheBlasfem in #5864)
• React DOM now warns if you specify onFocusIn or onFocusOut handlers as they are unnecessary in React. (@jontewks in #6296)
• React now prints a descriptive error message when you pass an invalid callback as the last argument to ReactDOM.render(), this.setState(), or this.forceUpdate(). (@conorhastings in #5193 and @gaearon in #6310)
• Add-Ons: TestUtils.Simulate() now prints a helpful message if you attempt to use it with shallow rendering. (@conorhastings in #5358)
• PropTypes: arrayOf() and objectOf() provide better error messages for invalid arguments. (@chicoxyzzy in #5390)

Notable bug fixes

• Fixed multiple small memory leaks. (@sophiebits in #4983 and @victor-homyakov in #6309)
• Input events are handled more reliably in IE 10 and IE 11; spurious events no longer fire when using a placeholder. (@jquense in #4051)
• The componentWillReceiveProps() lifecycle method is now consistently called when context changes. (@milesj in #5787)
• React.cloneElement() doesn’t append slash to an existing key when used inside React.Children.map(). (@ianobermiller in #5892)
• React DOM now supports the cite and profile HTML attributes. (@AprilArcus in #6094 and @saiichihashimoto in #6032)
• React DOM now supports cssFloat, gridRow and gridColumn CSS properties. (@stevenvachon in #6133 and @mnordick in #4779)
• React DOM now correctly handles borderImageOutset, borderImageWidth, borderImageSlice, floodOpacity, strokeDasharray, and strokeMiterlimit as unitless CSS properties. (@rofrischmann in #6210 and #6270)
• React DOM now supports the onAnimationStart, onAnimationEnd, onAnimationIteration, onTransitionEnd, and onInvalid events. Support for onLoad has been added to object elements. (@tomduncalf in #5187, @milesj in #6005, and @ara4n in #5781)
• React DOM now defaults to using DOM attributes instead of properties, which fixes a few edge case bugs. Additionally the nullification of values (ex: href={null}) now results in the forceful removal, no longer trying to set to the default value used by browsers in the absence of a value. (@syranide in #1510)
• React DOM does not mistakenly coerce children to strings for Web Components. (@jimfb in #5093)
• React DOM now correctly normalizes SVG <use> events. (@edmellum in #5720)
• React DOM does not throw if a <select> is unmounted while its onChange handler is executing. (@sambev in #6028)
• React DOM does not throw in Windows 8 apps. (@Andrew8xx8 in #6063)
• React DOM does not throw when asynchronously unmounting a child with a ref. (@yiminghe in #6095)
• React DOM no longer forces synchronous layout because of scroll position tracking. (@syranide in #2271)
• Object.is is used in a number of places to compare values, which leads to fewer false positives, especially involving NaN. In particular, this affects the shallowCompare add-on. (@chicoxyzzy in #6132)
• Add-Ons: ReactPerf no longer instruments adding or removing an event listener because they don’t really touch the DOM due to event delegation. (@antoaravinth in #5209)

Other improvements

• React now uses loose-envify instead of envify so it installs fewer transitive dependencies. (@qerub in #6303)
• Shallow renderer now exposes getMountedInstance(). (@glenjamin in #4918)
• Shallow renderer now returns the rendered output from render(). (@simonewebdesign in #5411)
• React no longer depends on ES5 shams for Object.create and Object.freeze in older environments. It still, however, requires ES5 shims in those environments. (@dgreensp in #4959)
• React DOM now allows data- attributes with names that start with numbers. (@nLight in #5216)
• React DOM adds a new suppressContentEditableWarning prop for components like Draft.js that intentionally manage contentEditable children with React. (@mxstbr in #6112)
• React improves the performance for createClass() on complex specs. (@sophiebits in #5550)