Releases: facebook/react
Releases · facebook/react
v0.14.5
v0.14.4
React
- Minor internal changes for better compatibility with React Native
React DOM
- The
autoCapitalizeandautoCorrectprops are now set as attributes in the DOM instead of properties to improve cross-browser compatibility - Fixed bug with controlled
<select>elements not handling updates properly
React Perf Add-on
- Some DOM operation names have been updated for clarity in the output of
.printDOM()
v0.14.3
React DOM
- Added support for
nonceattribute for<script>and<style>elements - Added support for
reversedattribute for<ol>elements
React TestUtils Add-on
- Fixed bug with shallow rendering and function refs
React CSSTransitionGroup Add-on
- Fixed bug resulting in timeouts firing incorrectly when mounting and unmounting rapidly
React on Bower
- Added
react-dom-server.jsto exposerenderToStringandrenderToStaticMarkupfor usage in the browser
v0.14.2
React DOM
- Fixed bug with development build preventing events from firing in some versions of Internet Explorer & Edge
- Fixed bug with development build when using es5-sham in older versions of Internet Explorer
- Added support for
integrityattribute - Fixed bug resulting in
childrenprop being coerced to a string for custom elements, which was not the desired behavior - Moved
reactfromdependenciestopeerDependenciesto match expectations and align withreact-addons-*packages
v0.14.1
React DOM
- Fixed bug where events wouldn't fire in old browsers when using React in development mode
- Fixed bug preventing use of
dangerouslySetInnerHTMLwith Closure Compiler Advanced mode - Added support for
srcLang,default, andkindattributes for<track>elements - Added support for
colorattribute - Ensured legacy
.propsaccess on DOM nodes is updated on re-renders
React TestUtils Add-on
- Fixed
scryRenderedDOMComponentsWithClassso it works with SVG
React CSSTransitionGroup Add-on
- Fix bug preventing
0to be used as a timeout value
React on Bower
- Added
react-dom.jstomainto improve compatibility with tooling
v0.14.0
v0.13.3
React Core
New Features
- Added
clipPathelement and attribute for SVG - Improved warnings for deprecated methods in plain JS classes
Bug Fixes
- Loosened
dangerouslySetInnerHTMLrestrictions so{__html: undefined}will no longer throw - Fixed extraneous context warning with non-pure
getChildContext - Ensure
replaceState(obj)retains prototype ofobj
React with Add-ons
Bug Fixes
- Test Utils: Ensure that shallow rendering works when components define
contextTypes
v0.13.2
React Core
New Features
- Added
strokeDashoffset,flexPositive,flexNegativeto the list of unitless CSS properties - Added support for more DOM properties:
scoped- for<style>elementshigh,low,optimum- for<meter>elementsunselectable- IE-specific property to prevent user selection
Bug Fixes
- Fixed a case where re-rendering after rendering null didn't properly pass context
- Fixed a case where re-rendering after rendering with
style={null}didn't properly updatestyle - Update
uglifydependency to prevent a bug in IE8 - Improved warnings
React with Add-Ons
Bug Fixes
- Immutabilty Helpers: Ensure it supports
hasOwnPropertyas an object key
React Tools
- Improve documentation for new options
v0.13.1
React Core
Bug Fixes
- Don't throw when rendering empty
<select>elements - Ensure updating
styleworks when transitioning fromnull
React with Add-Ons
Bug Fixes
- TestUtils: Don't warn about
getDOMNodefor ES6 classes - TestUtils: Ensure wrapped full page components (
<html>,<head>,<body>) are treated as DOM components - Perf: Stop double-counting DOM components
React Tools
Bug Fixes
- Fix option parsing for
--non-strict-es6module
v0.13.0
React Core
Breaking Changes
- Deprecated patterns that warned in 0.12 no longer work: most prominently, calling component classes without using JSX or React.createElement and using non-component functions with JSX or createElement
- Mutating
propsafter an element is created is deprecated and will cause warnings in development mode; future versions of React will incorporate performance optimizations assuming that props aren't mutated - Static methods (defined in
statics) are no longer autobound to the component class refresolution order has changed slightly such that a ref to a component is available immediately after itscomponentDidMountmethod is called; this change should be observable only if your component calls a parent component's callback within yourcomponentDidMount, which is an anti-pattern and should be avoided regardless- Calls to
setStatein life-cycle methods are now always batched and therefore asynchronous. Previously the first call on the first mount was synchronous. setStateandforceUpdateon an unmounted component now warns instead of throwing. That avoids a possible race condition with Promises.- Access to most internal properties has been completely removed, including
this._pendingStateandthis._rootNodeID.
New Features
- Support for using ES6 classes to build React components; see the v0.13.0 beta 1 notes for details.
- Added new top-level API
React.findDOMNode(component), which should be used in place ofcomponent.getDOMNode(). The base class for ES6-based components will not havegetDOMNode. This change will enable some more patterns moving forward. - Added a new top-level API
React.cloneElement(el, props)for making copies of React elements – see the v0.13 RC2 notes for more details. - New
refstyle, allowing a callback to be used in place of a name:<Photo ref={(c) => this._photo = c} />allows you to reference the component withthis._photo(as opposed toref="photo"which givesthis.refs.photo). this.setState()can now take a function as the first argument for transactional state updates, such asthis.setState((state, props) => ({count: state.count + 1}));– this means that you no longer need to usethis._pendingState, which is now gone.- Support for iterators and immutable-js sequences as children.
Deprecations
ComponentClass.typeis deprecated. Just useComponentClass(usually aselement.type === ComponentClass).- Some methods that are available on
createClass-based components are removed or deprecated from ES6 classes (getDOMNode,replaceState,isMounted,setProps,replaceProps).
React with Add-Ons
New Features
React.addons.createFragmentwas added for adding keys to entire sets of children.
Deprecations
React.addons.classSetis now deprecated. This functionality can be replaced with several freely available modules. classnames is one such module.- Calls to
React.addons.cloneWithPropscan be migrated to useReact.cloneElementinstead – make sure to mergestyleandclassNamemanually if desired.
React Tools
Breaking Changes
- When transforming ES6 syntax,
classmethods are no longer enumerable by default, which requiresObject.defineProperty; if you support browsers such as IE8, you can pass--target es3to mirror the old behavior
New Features
--targetoption is available on the jsx command, allowing users to specify and ECMAScript version to target.es5is the default.es3restores the previous default behavior. An additional transform is added here to ensure the use of reserved words as properties is safe (egthis.staticwill becomethis['static']for IE8 compatibility).
- The transform for the call spread operator has also been enabled.
JSX
Breaking Changes
- A change was made to how some JSX was parsed, specifically around the use of
>or}when inside an element. Previously it would be treated as a string but now it will be treated as a parse error. Thejsx_orphaned_brackets_transformerpackage on npm can be used to find and fix potential issues in your JSX code.