All Versions
102
Latest Version
Avg Release Cycle
56 days
Latest Release
675 days ago
Changelog History
Page 9
Changelog History
Page 9
-
v0.13.1 Changes
March 16, 2015React Core
π Bug Fixes
- Don't throw when rendering empty
<select>
elements - π
Ensure updating
style
works when transitioning fromnull
React with Add-Ons
π Bug Fixes
- β
TestUtils: Don't warn about
getDOMNode
for 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
- Don't throw when rendering empty
-
v0.13.0 Changes
March 10, 2015React 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
props
after 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 ref
resolution order has changed slightly such that a ref to a component is available immediately after itscomponentDidMount
method 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
setState
in life-cycle methods are now always batched and therefore asynchronous. Previously the first call on the first mount was synchronous. - β‘οΈ
setState
andforceUpdate
on 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._pendingState
andthis._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
ref
style, 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.type
is 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.createFragment
was added for adding keys to entire sets of children.
π Deprecations
- π¦
React.addons.classSet
is now deprecated. This functionality can be replaced with several freely available modules. classnames is one such module. - π
Calls to
React.addons.cloneWithProps
can be migrated to useReact.cloneElement
instead β make sure to mergestyle
andclassName
manually if desired.
React Tools
π₯ Breaking Changes
- 0οΈβ£ When transforming ES6 syntax,
class
methods are no longer enumerable by default, which requiresObject.defineProperty
; if you support browsers such as IE8, you can pass--target es3
to mirror the old behavior
π New Features
--target
option is available on the jsx command, allowing users to specify and ECMAScript version to target.es5
is the default.es3
restores the previous default behavior. An additional transform is added here to ensure the use of reserved words as properties is safe (egthis.static
will becomethis['static']
for IE8 compatibility).
- The transform for the call spread operator has also been enabled.
JSXTransformer
π₯ Breaking Changes
- The return value of
transform
now containssourceMap
as a JS object already, not an instance ofSourceMapGenerator
.
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_transformer
package on npm can be used to find and fix potential issues in your JSX code.
-
v0.12.2 Changes
December 18, 2014React Core
- β Added support for more HTML attributes:
formAction
,formEncType
,formMethod
,formTarget
,marginHeight
,marginWidth
- β Added
strokeOpacity
to 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
undefined
toReact.createElement
- now there is a useful warning
React Tools
- JSX-related transforms now always use double quotes for props and
displayName
- β Added support for more HTML attributes:
-
v0.12.1 Changes
November 18, 2014React 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
-
v0.12.0 Changes
October 28, 2014React Core
π₯ Breaking Changes
- π
key
andref
moved 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.__internals
is 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.createFactory
first. 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.render
React.renderComponentToString
-->React.renderToString
React.renderComponentToStaticMarkup
-->React.renderToStaticMarkup
React.isValidComponent
-->React.isValidElement
React.PropTypes.component
-->React.PropTypes.element
React.PropTypes.renderable
-->React.PropTypes.node
- π DEPRECATED
React.isValidClass
- π DEPRECATED
instance.transferPropsTo
- π DEPRECATED Returning
false
from 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.getModifierState
as 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:
list
updates correctly nowscrollLeft
,scrollTop
removed, these should not be specified as props
- π Improved error messages
React With Addons
π New Features
- β‘οΈ
React.addons.batchedUpdates
added to API for hooking into update cycle
π₯ Breaking Changes
- β‘οΈ
React.addons.update
usesassign
instead ofcopyProperties
which doeshasOwnProperty
checks. 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.DOM
no 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)
- π
-
v0.11.2 Changes
September 16, 2014React Core
π New Features
- β Added support for
<dialog>
element and associatedopen
attribute - β Added support for
<picture>
element and associatedmedia
andsizes
attributes - β Added
React.createElement
API in preparation for React v0.12React.createDescriptor
has been deprecated as a result
JSX
- π
<picture>
is now parsed intoReact.DOM.picture
React Tools
- β‘οΈ Update
esprima
andjstransform
for correctness fixes - π The
jsx
executable now exposes a--strip-types
flag which can be used to remove TypeScript-like type annotations- This option is also exposed to
require('react-tools').transform
asstripTypes
- This option is also exposed to
- β Added support for
-
v0.11.1 Changes
July 24, 2014React Core
π Bug Fixes
setState
can be called insidecomponentWillMount
in non-DOM environments- π
SyntheticMouseEvent.getEventModifierState
correctly renamed togetModifierState
getModifierState
correctly returns aboolean
getModifierState
is now correctly case sensitive- π Empty Text node used in IE8
innerHTML
workaround is now removed, fixing rerendering in certain cases
JSX
- π Fix duplicate variable declaration in JSXTransformer (caused issues in some browsers)
-
v0.11.0 Changes
July 17, 2014React Core
π₯ Breaking Changes
- 0οΈβ£
getDefaultProps()
is now called once per class and shared across all instances MyComponent()
now returns a descriptor, not an instanceReact.isValidComponent
andReact.PropTypes.component
validate descriptors, not component instances- π² Custom
propType
validators should return anError
instead of logging directly
π New Features
- 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
π Bug Fixes
- 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
React With Addons
- β‘οΈ 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
React NPM Module
- π¦ Now includes the pre-built packages under
dist/
. envify
is properly listed as a dependency instead of a peer dependency
JSX
- β 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
React Tools Module
- π 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
- 0οΈβ£
-
v0.10.0 Changes
March 21, 2014React 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:
srcSet
for<img>
to specify images at different pixel ratiostextAnchor
for SVG
π Bug Fixes
- 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.
β Addons
- β‘οΈ
update
function to deal with immutable data. Read the docs
react-tools
- β 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.
-
v0.9.0 Changes
February 20, 2014React Core
π₯ Breaking Changes
- β‘οΈ The lifecycle methods
componentDidMount
andcomponentDidUpdate
no longer receive the root node as a parameter; usethis.getDOMNode()
instead - 0οΈβ£ 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 removed - π
React.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
π 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:
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
π Bug Fixes
- 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 with Addons
- β
React.addons.TestUtils
was added to help write unit tests React.addons.TransitionGroup
was renamed toReact.addons.CSSTransitionGroup
React.addons.TransitionGroup
was added as a more general animation wrapper- π―
React.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
π¦ 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-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 browsers - π
JSXTransformer
error messages now include the filename and problematic line contents when a file fails to parse
- β‘οΈ The lifecycle methods