React v0
https://github.com/facebook/react
React
- Fixed bug with
<option>tags when usingdangerouslySetInnerHTML - Fixed memory leak in synthetic event system
React TestUtils Add-on
- Fixed bug with calling
setStateincomponentWillMountwhen using shallow rendering
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()
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
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
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
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
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
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
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.
React Core
- Added support for more HTML attributes:
formAction,formEncType,formMethod,formTarget,marginHeight,marginWidth - Added
strokeOpacityto the list of unitless CSS properties - Removed trailing commas (allows npm module to be bundled and used in IE8)
- Fixed bug resulting in error when passing
undefinedtoReact.createElement- now there is a useful warning
React Tools
- JSX-related transforms now always use double quotes for props and
displayName
React Tools
- Types transform updated with latest support
- jstransform version updated with improved ES6 transforms
- Explicit Esprima dependency removed in favor of using Esprima information exported by jstransform
React Core
Breaking Changes
keyandrefmoved off props object, now accessible on the element directly- React is now BSD licensed with accompanying Patents grant
- Default prop resolution has moved to Element creation time instead of mount time, making them effectively static
React.__internalsis removed - it was exposed for DevTools which no longer needs access- Composite Component functions can no longer be called directly - they must be wrapped with
React.createFactoryfirst. This is handled for you when using JSX.
New Features
- Spread operator (
{...}) introduced to deprecatethis.transferPropsTo - Added support for more HTML attributes:
acceptCharset,classID,manifest
Deprecations
React.renderComponent-->React.renderReact.renderComponentToString-->React.renderToStringReact.renderComponentToStaticMarkup-->React.renderToStaticMarkupReact.isValidComponent-->React.isValidElementReact.PropTypes.component-->React.PropTypes.elementReact.PropTypes.renderable-->React.PropTypes.node- DEPRECATED
React.isValidClass - DEPRECATED
instance.transferPropsTo - DEPRECATED Returning
falsefrom event handlers to preventDefault - DEPRECATED Convenience Constructor usage as function, instead wrap with
React.createFactory - DEPRECATED use of
key={null}to assign implicit keys
Bug Fixes
- Better handling of events and updates in nested results, fixing value restoration in "layered" controlled components
- Correctly treat
event.getModifierStateas case sensitive - Improved normalization of
event.charCode - Better error stacks when involving autobound methods
- Removed DevTools message when the DevTools are installed
- Correctly detect required language features across browsers
- Fixed support for some HTML attributes:
listupdates correctly nowscrollLeft,scrollTopremoved, these should not be specified as props
- Improved error messages
React With Addons
New Features
React.addons.batchedUpdatesadded to API for hooking into update cycle
Breaking Changes
React.addons.updateusesassigninstead ofcopyPropertieswhich doeshasOwnPropertychecks. Properties on prototypes will no longer be updated correctly.
Bug Fixes
- Fixed some issues with CSS Transitions
JSX
Breaking Changes
- Enforced convention: lower case tag names are always treated as HTML tags, upper case tag names are always treated as composite components
- JSX no longer transforms to simple function calls
New Features
@jsx React.DOMno longer required- spread (
{...}) operator introduced to allow easier use of props
Bug Fixes
- JSXTransformer: Make sourcemaps an option when using APIs directly (eg, for react-rails)
React Core
New Features
- Added support for
<dialog>element and associatedopenattribute - Added support for
<picture>element and associatedmediaandsizesattributes - Added
React.createElementAPI in preparation for React v0.12React.createDescriptorhas been deprecated as a result
JSX
<picture>is now parsed intoReact.DOM.picture
React Tools
- Update
esprimaandjstransformfor correctness fixes - The
jsxexecutable now exposes a--strip-typesflag which can be used to remove TypeScript-like type annotations- This option is also exposed to
require('react-tools').transformasstripTypes
- This option is also exposed to
React Core
Bug Fixes
setStatecan be called insidecomponentWillMountin non-DOM environmentsSyntheticMouseEvent.getEventModifierStatecorrectly renamed togetModifierStategetModifierStatecorrectly returns abooleangetModifierStateis now correctly case sensitive- Empty Text node used in IE8
innerHTMLworkaround is now removed, fixing rerendering in certain cases
JSX
- Fix duplicate variable declaration in JSXTransformer (caused issues in some browsers)
React Core
Breaking Changes
getDefaultProps()is now called once per class and shared across all instancesMyComponent()now returns a descriptor, not an instanceReact.isValidComponentandReact.PropTypes.componentvalidate descriptors, not component instances- Custom
propTypevalidators should return anErrorinstead of logging directly
New Features
- Rendering to
null - Keyboard events include normalized
e.keyande.getModifierState()properties - New normalized
onBeforeInputevent React.Children.counthas been added as a helper for counting the number of children
Bug Fixes
- Re-renders are batched in more cases
- Events:
e.viewproperly normalized - Added Support for more HTML attributes (
coords,crossOrigin,download,hrefLang,mediaGroup,muted,scrolling,shape,srcSet,start,useMap) - Improved SVG support
- Changing
classNameon a mounted SVG component now works correctly - Added support for elements
maskandtspan - Added support for attributes
dx,dy,fillOpacity,fontFamily,fontSize,markerEnd,markerMid,markerStart,opacity,patternContentUnits,patternUnits,preserveAspectRatio,strokeDasharray,strokeOpacity
- Changing
- CSS property names with vendor prefixes (
Webkit,ms,Moz,O) are now handled properly - Duplicate keys no longer cause a hard error; now a warning is logged (and only one of the children with the same key is shown)
imgevent listeners are now unbound properly, preventing the error "Two valid but unequal nodes with the samedata-reactid"- Added explicit warning when missing polyfills
React With Addons
- PureRenderMixin: a mixin which helps optimize "pure" components
- Perf: a new set of tools to help with performance analysis
- Update: New
$applycommand to transform values - TransitionGroup bug fixes with null elements, Android
React NPM Module
- Now includes the pre-built packages under
dist/. envifyis properly listed as a dependency instead of a peer dependency
JSX
- Added support for namespaces, eg
<Components.Checkbox /> - JSXTransformer
- Enable the same
harmonyfeatures available in the command line with<script type="text/jsx;harmony=true"> - Scripts are downloaded in parallel for more speed. They are still executed in order (as you would expect with normal script tags)
- Fixed a bug preventing sourcemaps from working in Firefox
- Enable the same
React Tools Module
- Improved readme with usage and API information
- Improved ES6 transforms available with
--harmonyoption - Added
--source-map-inlineoption to thejsxexecutable - New
transformWithDetailsAPI which gives access to the raw sourcemap data
React Core
New Features
- Added warnings to help migrate towards descriptors
- Made it possible to server render without React-related markup (
data-reactid,data-react-checksum). This DOM will not be mountable by React. Read the docs forReact.renderComponentToStaticMarkup - Added support for more attributes:
srcSetfor<img>to specify images at different pixel ratiostextAnchorfor SVG
Bug Fixes
- Ensure all void elements don’t insert a closing tag into the markup.
- Ensure
className={false}behaves consistently - Ensure
this.refsis defined, even if no refs are specified.
Addons
updatefunction to deal with immutable data. Read the docs
react-tools
- Added an option argument to
transformfunction. The only option supported isharmony, which behaves the same asjsx --harmonyon the command line. This uses the ES6 transforms from jstransform.
What’s New?
This version includes better support for normalizing event properties across all supported browsers so that you need to worry even less about cross-browser differences. We've also made many improvements to error messages and have refactored the core to never rethrow errors, so stack traces are more accurate and Chrome's purple break-on-error stop sign now works properly.
We've also added to the add-ons build React.addons.TestUtils, a set of new utilities to help you write unit tests for React components. You can now simulate events on your components, and several helpers are provided to help make assertions about the rendered DOM tree.
We've also made several other improvements and a few breaking changes; the full changelog is provided below.
JSX Whitespace
In addition to the changes to React core listed below, we've made a small change to the way JSX interprets whitespace to make things more consistent. With this release, space between two components on the same line will be preserved, while a newline separating a text node from a tag will be eliminated in the output. Consider the code:
<div>
Monkeys:
{listOfMonkeys} {submitButton}
</div>
In v0.8 and below, it was transformed to the following:
React.DOM.div(null,
" Monkeys: ",
listOfMonkeys, submitButton
)
In v0.9, it will be transformed to this JS instead:
React.DOM.div(null,
"Monkeys:",
listOfMonkeys, " ", submitButton
)
We believe this new behavior is more helpful and elimates cases where unwanted whitespace was previously added.
In cases where you want to preserve the space adjacent to a newline, you can write {'Monkeys: '} or Monkeys:{' '} in your JSX source. We've included a script to do an automated codemod of your JSX source tree that preserves the old whitespace behavior by adding and removing spaces appropriately. You can install jsx_whitespace_transformer from npm and run it over your source tree to modify files in place. The transformed JSX files will preserve your code's existing whitespace behavior.
Changelog
React Core
Breaking Changes
- The lifecycle methods
componentDidMountandcomponentDidUpdateno longer receive the root node as a parameter; usethis.getDOMNode()instead - Whenever a prop is equal to
undefined, the default value returned bygetDefaultPropswill now be used instead React.unmountAndReleaseReactRootNodewas previously deprecated and has now been removedReact.renderComponentToStringis now synchronous and returns the generated HTML string- Full-page rendering (that is, rendering the
<html>tag using React) is now supported only when starting with server-rendered markup - On mouse wheel events,
deltaYis no longer negated - When prop types validation fails, a warning is logged instead of an error thrown (with the production build of React, type checks are now skipped for performance)
- On
input,select, andtextareaelements,.getValue()is no longer supported; use.getDOMNode().valueinstead
New Features
- React now never rethrows errors, so stack traces are more accurate and Chrome's purple break-on-error stop sign now works properly
- Added support for SVG tags
defs,linearGradient,polygon,radialGradient,stop - Added support for more attributes:
crossOriginfor CORS requestsdownloadandhrefLangfor<a>tagsmediaGroupandmutedfor<audio>and<video>tagsnoValidateandformNoValidatefor formspropertyfor Open Graph<meta>tagssandbox,seamless, andsrcDocfor<iframe>tagsscopefor screen readersspanfor<colgroup>tags
- Added support for defining
propTypesin mixins - Added
any,arrayOf,component,oneOfType,renderable,shapetoReact.PropTypes - Added support for
staticson component spec for static component methods - On all events,
.currentTargetis now properly set - On keyboard events,
.keyis now polyfilled in all browsers for special (non-printable) keys - On clipboard events,
.clipboardDatais now polyfilled in IE - On drag events,
.dragTransferis now present - Added support for
onMouseOverandonMouseOutin addition to the existingonMouseEnterandonMouseLeaveevents - Added support for
onLoadandonErroron<img>elements - Added support for
onReseton<form>elements - The
autoFocusattribute is now polyfilled consistently oninput,select, andtextarea
Bug Fixes
- React no longer adds an
__owner__property to each component'spropsobject; passed-in props are now never mutated - When nesting top-level components (e.g., calling
React.renderComponentwithincomponentDidMount), events now properly bubble to the parent component - Fixed a case where nesting top-level components would throw an error when updating
- Passing an invalid or misspelled propTypes type now throws an error
- On mouse enter/leave events,
.target,.relatedTarget, and.typeare now set properly - On composition events,
.datais now properly normalized in IE9 and IE10 - CSS property values no longer have
pxappended for the unitless propertiescolumnCount,flex,flexGrow,flexShrink,lineClamp,order,widows - Fixed a memory leak when unmounting children with a
componentWillUnmounthandler - Fixed a memory leak when
renderComponentToStringwould store event handlers - Fixed an error that could be thrown when removing form elements during a click handler
- Boolean attributes such as
disabledare rendered without a value (previouslydisabled="true", now simplydisabled) keyvalues containing.are now supported- Shortened
data-reactidvalues for performance - Components now always remount when the
keyproperty changes - Event handlers are attached to
documentonly when necessary, improving performance in some cases - Events no longer use
.returnValuein modern browsers, eliminating a warning in Chrome scrollLeftandscrollTopare no longer accessed on document.body, eliminating a warning in Chrome- General performance fixes, memory optimizations, improvements to warnings and error messages
React with Addons
React.addons.TestUtilswas added to help write unit testsReact.addons.TransitionGroupwas renamed toReact.addons.CSSTransitionGroupReact.addons.TransitionGroupwas added as a more general animation wrapperReact.addons.cloneWithPropswas added for cloning components and modifying their props- Bug fix for adding back nodes during an exit transition for CSSTransitionGroup
- Bug fix for changing
transitionLeavein CSSTransitionGroup - Performance optimizations for CSSTransitionGroup
- On checkbox
<input>elements,checkedLinkis now supported for two-way binding
JSX Compiler and react-tools Package
- Whitespace normalization has changed; now space between two tags on the same line will be preserved, while newlines between two tags will be removed
- The
react-toolsnpm package no longer includes the React core libraries; use thereactpackage instead. displayNameis now added in more cases, improving error messages and names in the React Dev Tools- Fixed an issue where an invalid token error was thrown after a JSX closing tag
JSXTransformernow uses source maps automatically in modern browsersJSXTransformererror messages now include the filename and problematic line contents when a file fails to parse
Now installable via npm!
$ npm install react
React
- Added support for more attributes:
rows&colsfor<textarea>defer&asyncfor<script>loopfor<audio>&<video>autoCorrectfor form fields (a non-standard attribute only supported by mobile WebKit)
- Improved error messages
- Fixed Selection events in IE11
- Added
onContextMenuevents
React with Addons
- Fixed bugs with TransitionGroup when children were undefined
- Added support for
onTransition
react-tools
- Upgraded
jstransformandesprima-fb
JSXTransformer
- Added support for use in IE8
- Upgraded browserify, which reduced file size by ~65KB (16KB gzipped)
React
- Fixed bug with
<input type="range">and selection events. - Fixed bug with selection and focus.
- Made it possible to unmount components from the document root.
- Fixed bug for
disabledattribute handling on non-<input>elements.
React with Addons
- Fixed bug with transition and animation event detection.
React
- Memory usage improvements - reduced allocations in core which will help with GC pauses
- Performance improvements - in addition to speeding things up, we made some tweaks to stay out of slow path code in V8 and Nitro.
- Standardized prop -> DOM attribute process. This previously resulting in additional type checking and overhead as well as confusing cases for users. Now we will always convert your value to a string before inserting it into the DOM.
- Support for Selection events.
- Support for Composition events.
- Support for additional DOM properties (
charSet,content,form,httpEquiv,rowSpan,autoCapitalize). - Support for additional SVG properties (
rx,ry). - Support for using
getInitialStateandgetDefaultPropsin mixins. - Support mounting into iframes.
- Bug fixes for controlled form components.
- Bug fixes for SVG element creation.
- Added
React.version. - Added
React.isValidClass- Used to determine if a value is a valid component constructor. - Removed
React.autoBind- This was deprecated in v0.4 and now properly removed. - Renamed
React.unmountAndReleaseReactRootNodetoReact.unmountComponentAtNode. - Began laying down work for refined performance analysis.
- Better support for server-side rendering - react-page has helped improve the stability for server-side rendering.
- Made it possible to use React in environments enforcing a strict Content Security Policy. This also makes it possible to use React to build Chrome extensions.
React with Addons (New!)
- Introduced a separate build with several "addons" which we think can help improve the React experience. We plan to deprecate this in the long-term, instead shipping each as standalone pieces. Read more in the docs.
JSX
- No longer transform
classtoclassNameas part of the transform! This is a breaking change - if you were usingclass, you must change this toclassNameor your components will be visually broken. - Added warnings to the in-browser transformer to make it clear it is not intended for production use.
- Improved compatibility for Windows
- Improved support for maintaining line numbers when transforming.
React
setStatecallbacks are now executed in the scope of your component.clickevents now work on Mobile Safari.- Prevent a potential error in event handling if
Object.prototypeis extended. - Don't set DOM attributes to the string
"undefined"on update when previously defined. - Improved support for
<iframe>attributes. - Added checksums to detect and correct cases where server-side rendering markup mismatches what React expects client-side.
JSXTransformer
- Improved environment detection so it can be run in a non-browser environment.
React
- Switch from using
idattribute todata-reactidto track DOM nodes. This allows you to integrate with other JS and CSS libraries more easily. - Support for more DOM elements and attributes (e.g.,
<canvas>) - Improved server-side rendering APIs.
React.renderComponentToString(<component>, callback)allows you to use React on the server and generate markup which can be sent down to the browser. propimprovements: validation and default values. Read our blog post for details...- Support for the
keyprop, which allows for finer control over reconciliation. Read the docs for details... - Removed
React.autoBind. Read our blog post for details... - Improvements to forms. We've written wrappers around
<input>,<textarea>,<option>, and<select>in order to standardize many inconsistencies in browser implementations. This includes support fordefaultValue, and improved implementation of theonChangeevent, and circuit completion. Read the docs for details... - We've implemented an improved synthetic event system that conforms to the W3C spec.
- Updates to your component are batched now, which may result in a significantly faster re-render of components.
this.setStatenow takes an optional callback as it's second parameter. If you were usingonClick={this.setState.bind(this, state)}previously, you'll want to make sure you add a third parameter so that the event is not treated as the callback.
JSX
- Support for comment nodes
<div>{/* this is a comment and won't be rendered */}</div> - Children are now transformed directly into arguments instead of being wrapped in an array
E.g.<div><Component1/><Component2/></div>is transformed intoReact.DOM.div(null, Component1(null), Component2(null)).
Previously this would be transformed intoReact.DOM.div(null, [Component1(null), Component2(null)]).
If you were using React without JSX previously, your code should still work.
react-tools
- Fixed a number of bugs when transforming directories
- No longer re-write
require()s to be relative unless specified
This release addresses some small issues people were having and simplifies our tools to make them easier to use.
react-tools
- Upgrade Commoner so
requirestatements are no longer relativized when passing through the transformer. This was a feature needed when building React, but doesn't translate well for other consumers ofbin/jsx. - Upgraded our dependencies on Commoner and Recast so they use a different directory for their cache.
- Freeze our esprima dependency.
React
- Allow reusing the same DOM node to render different components. e.g.
React.renderComponent(<div/>, domNode); React.renderComponent(<span/>, domNode);will work now.
JSXTransformer
- Improved the in-browser transformer so that transformed scripts will execute in the expected scope. The allows components to be defined and used from separate files.