getDefaultProps()
is now called once per class and shared across all instances
- Rendering to
null
- Keyboard events include normalized
e.key
ande.getModifierState()
properties - New normalized
onBeforeInput
event React.Children.count
has been added as a helper for counting the number of children
- Re-renders are batched in more cases
- Events:
e.view
properly normalized - Added Support for more HTML attributes (
coords
,crossOrigin
,download
,hrefLang
,mediaGroup
,muted
,scrolling
,shape
,srcSet
,start
,useMap
) - Improved SVG support
- Changing
className
on a mounted SVG component now works correctly - Added support for elements
mask
andtspan
- 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)
img
event listeners are now unbound properly, preventing the error "Two valid but unequal nodes with the samedata-reactid
"- Added explicit warning when missing polyfills
- PureRenderMixin: a mixin which helps optimize "pure" components
- Perf: a new set of tools to help with performance analysis
- Update: New
$apply
command to transform values - TransitionGroup bug fixes with null elements, Android
- Now includes the pre-built packages under
dist/
. envify
is properly listed as a dependency instead of a peer dependency
- Added support for namespaces, eg
<Components.Checkbox />
- JSXTransformer
- Enable the same
harmony
features 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
- Improved readme with usage and API information
- Improved ES6 transforms available with
--harmony
option - Added
--source-map-inline
option to thejsx
executable - New
transformWithDetails
API which gives access to the raw sourcemap data
- 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:
srcSet
for<img>
to specify images at different pixel ratiostextAnchor
for SVG
- Ensure all void elements don’t insert a closing tag into the markup.
- Ensure
className={false}
behaves consistently - Ensure
this.refs
is defined, even if no refs are specified.
update
function to deal with immutable data. Read the docs
- Added an option argument to
transform
function. The only option supported isharmony
, which behaves the same asjsx --harmony
on the command line. This uses the ES6 transforms from jstransform.
- The lifecycle methods
componentDidMount
andcomponentDidUpdate
no longer receive the root node as a parameter; usethis.getDOMNode()
instead - Whenever a prop is equal to
undefined
, the default value returned bygetDefaultProps
will now be used instead React.unmountAndReleaseReactRootNode
was previously deprecated and has now been removedReact.renderComponentToString
is 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,
deltaY
is 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
, andtextarea
elements,.getValue()
is no longer supported; use.getDOMNode().value
instead this.context
on components is now reserved for internal use by React
- 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:
crossOrigin
for CORS requestsdownload
andhrefLang
for<a>
tagsmediaGroup
andmuted
for<audio>
and<video>
tagsnoValidate
andformNoValidate
for formsproperty
for Open Graph<meta>
tagssandbox
,seamless
, andsrcDoc
for<iframe>
tagsscope
for screen readersspan
for<colgroup>
tags
- Added support for defining
propTypes
in mixins - Added
any
,arrayOf
,component
,oneOfType
,renderable
,shape
toReact.PropTypes
- Added support for
statics
on component spec for static component methods - On all events,
.currentTarget
is now properly set - On keyboard events,
.key
is now polyfilled in all browsers for special (non-printable) keys - On clipboard events,
.clipboardData
is now polyfilled in IE - On drag events,
.dragTransfer
is now present - Added support for
onMouseOver
andonMouseOut
in addition to the existingonMouseEnter
andonMouseLeave
events - Added support for
onLoad
andonError
on<img>
elements - Added support for
onReset
on<form>
elements - The
autoFocus
attribute is now polyfilled consistently oninput
,select
, andtextarea
- React no longer adds an
__owner__
property to each component'sprops
object; passed-in props are now never mutated - When nesting top-level components (e.g., calling
React.renderComponent
withincomponentDidMount
), 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.type
are now set properly - On composition events,
.data
is now properly normalized in IE9 and IE10 - CSS property values no longer have
px
appended for the unitless propertiescolumnCount
,flex
,flexGrow
,flexShrink
,lineClamp
,order
,widows
- Fixed a memory leak when unmounting children with a
componentWillUnmount
handler - Fixed a memory leak when
renderComponentToString
would store event handlers - Fixed an error that could be thrown when removing form elements during a click handler
- Boolean attributes such as
disabled
are rendered without a value (previouslydisabled="true"
, now simplydisabled
) key
values containing.
are now supported- Shortened
data-reactid
values for performance - Components now always remount when the
key
property changes - Event handlers are attached to
document
only when necessary, improving performance in some cases - Events no longer use
.returnValue
in modern browsers, eliminating a warning in Chrome scrollLeft
andscrollTop
are no longer accessed on document.body, eliminating a warning in Chrome- General performance fixes, memory optimizations, improvements to warnings and error messages
React.addons.TestUtils
was added to help write unit testsReact.addons.TransitionGroup
was renamed toReact.addons.CSSTransitionGroup
React.addons.TransitionGroup
was added as a more general animation wrapperReact.addons.cloneWithProps
was added for cloning components and modifying their props- Bug fix for adding back nodes during an exit transition for CSSTransitionGroup
- Bug fix for changing
transitionLeave
in CSSTransitionGroup - Performance optimizations for CSSTransitionGroup
- On checkbox
<input>
elements,checkedLink
is now supported for two-way binding
- 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-tools
npm package no longer includes the React core libraries; use thereact
package instead. displayName
is 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
JSXTransformer
now uses source maps automatically in modern browsersJSXTransformer
error messages now include the filename and problematic line contents when a file fails to parse
- Added support for more attributes:
rows
&cols
for<textarea>
defer
&async
for<script>
loop
for<audio>
&<video>
autoCorrect
for form fields (a non-standard attribute only supported by mobile WebKit)
- Improved error messages
- Fixed Selection events in IE11
- Added
onContextMenu
events
- Fixed bugs with TransitionGroup when children were undefined
- Added support for
onTransition
- Upgraded
jstransform
andesprima-fb
- Added support for use in IE8
- Upgraded browserify, which reduced file size by ~65KB (16KB gzipped)
- Fixed a potential XSS vulnerability when using user content as a
key
: CVE-2013-7035
- 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
disabled
attribute handling on non-<input>
elements.
- Fixed bug with transition and animation event detection.
- 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
getInitialState
andgetDefaultProps
in 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.unmountAndReleaseReactRootNode
toReact.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.
- 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.
- No longer transform
class
toclassName
as part of the transform! This is a breaking change - if you were usingclass
, you must change this toclassName
or 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.
setState
callbacks are now executed in the scope of your component.click
events now work on Mobile Safari.- Prevent a potential error in event handling if
Object.prototype
is 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.
- Improved environment detection so it can be run in a non-browser environment.
- Switch from using
id
attribute todata-reactid
to 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. prop
improvements: validation and default values. Read our blog post for details...- Support for the
key
prop, 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 theonChange
event, 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.setState
now 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.
- 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.
- Fixed a number of bugs when transforming directories
- No longer re-write
require()
s to be relative unless specified
- Allow reusing the same DOM node to render different components. e.g.
React.renderComponent(<div/>, domNode); React.renderComponent(<span/>, domNode);
will work now.
- 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.
- Upgrade Commoner so
require
statements 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.
- Improved compatability with other coding styles (specifically, multiple assignments with a single
var
).
- Switch from using the browserified build to shipping individual modules. This allows react-tools to be used with browserify.
- Fix bug in packaging resulting in broken module.
- Initial public release