Sourced from react-refresh's releases.
v0.14.0
See http://facebook.github.io/react/blog/2015/10/07/react-v0.14.html.
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 ofobjReact with Add-ons
Bug Fixes
- Test Utils: Ensure that shallow rendering works when components define
contextTypesv0.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 selectionBug 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 keyReact 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
... (truncated)
Sourced from react-refresh's changelog.
0.14.0 (October 7, 2015)
Major changes
- Split the main
reactpackage into two:reactandreact-dom. This paves the way to writing components that can be shared between the web version of React and React Native. This means you will need to include both files and some functions have been moved fromReacttoReactDOM.- Addons have been moved to separate packages (
react-addons-clone-with-props,react-addons-create-fragment,react-addons-css-transition-group,react-addons-linked-state-mixin,react-addons-perf,react-addons-pure-render-mixin,react-addons-shallow-compare,react-addons-test-utils,react-addons-transition-group,react-addons-update,ReactDOM.unstable_batchedUpdates).- Stateless functional components - React components were previously created using React.createClass or using ES6 classes. This release adds a new syntax where a user defines a single stateless render function (with one parameter:
props) which returns a JSX element, and this function may be used as a component.- Refs to DOM components as the DOM node itself. Previously the only useful thing you can do with a DOM component is call
getDOMNode()to get the underlying DOM node. Starting with this release, a ref to a DOM component is the actual DOM node. Note that refs to custom (user-defined) components work exactly as before; only the built-in DOM components are affected by this change.Breaking changes
React.initializeTouchEventsis no longer necessary and has been removed completely. Touch events now work automatically.- Add-Ons: Due to the DOM node refs change mentioned above,
TestUtils.findAllInRenderedTreeand related helpers are no longer able to take a DOM component, only a custom component.- The
propsobject is now frozen, so mutating props after creating a component element is no longer supported. In most cases,React.cloneElementshould be used instead. This change makes your components easier to reason about and enables the compiler optimizations mentioned above.- Plain objects are no longer supported as React children; arrays should be used instead. You can use the
createFragmenthelper to migrate, which now returns an array.- Add-Ons:
classSethas been removed. Use classnames instead.- Web components (custom elements) now use native property names. Eg:
classinstead ofclassName.Deprecations
this.getDOMNode()is now deprecated andReactDOM.findDOMNode(this)can be used instead. Note that in the common case,findDOMNodeis now unnecessary since a ref to the DOM component is now the actual DOM node.setPropsandreplacePropsare now deprecated. Instead, call ReactDOM.render again at the top level with the new props.- ES6 component classes must now extend
React.Componentin order to enable stateless function components. The ES3 module pattern will continue to work.- Reusing and mutating a
styleobject between renders has been deprecated. This mirrors our change to freeze thepropsobject.- Add-Ons:
cloneWithPropsis now deprecated. UseReact.cloneElementinstead (unlikecloneWithProps,cloneElementdoes not mergeclassNameorstyleautomatically; you can merge them manually if needed).- Add-Ons: To improve reliability,
CSSTransitionGroupwill no longer listen to transition events. Instead, you should specify transition durations manually using props such astransitionEnterTimeout={500}.Notable enhancements
- Added
React.Children.toArraywhich takes a nested children object and returns a flat array with keys assigned to each child. This helper makes it easier to manipulate collections of children in yourrendermethods, especially if you want to reorder or slicethis.props.childrenbefore passing it down. In addition,React.Children.mapnow returns plain arrays too.- React uses
console.errorinstead ofconsole.warnfor warnings so that browsers show a full stack trace in the console. (Our warnings appear when you use patterns that will break in future releases and for code that is likely to behave unexpectedly, so we do consider our warnings to be “must-fix” errors.)- Previously, including untrusted objects as React children could result in an XSS security vulnerability. This problem should be avoided by properly validating input at the application layer and by never passing untrusted objects around your application code. As an additional layer of protection, React now tags elements with a specific ES2015 (ES6)
Symbolin browsers that support it, in order to ensure that React never considers untrusted JSON to be a valid element. If this extra security protection is important to you, you should add aSymbolpolyfill for older browsers, such as the one included by Babel’s polyfill.- When possible, React DOM now generates XHTML-compatible markup.
- React DOM now supports these standard HTML attributes:
capture,challenge,inputMode,is,keyParams,keyType,minLength,summary,wrap. It also now supports these non-standard attributes:autoSave,results,security.- React DOM now supports these SVG attributes, which render into namespaced attributes:
xlinkActuate,xlinkArcrole,xlinkHref,xlinkRole,xlinkShow,xlinkTitle,xlinkType,xmlBase,xmlLang,xmlSpace.- The
imageSVG tag is now supported by React DOM.- In React DOM, arbitrary attributes are supported on custom elements (those with a hyphen in the tag name or an
is="..."attribute).- React DOM now supports these media events on
audioandvideotags:onAbort,onCanPlay,onCanPlayThrough,onDurationChange,onEmptied,onEncrypted,onEnded,onError,onLoadedData,onLoadedMetadata,onLoadStart,onPause,onPlay,onPlaying,onProgress,onRateChange,onSeeked,onSeeking,onStalled,onSuspend,onTimeUpdate,onVolumeChange,onWaiting.- Many small performance improvements have been made.
- Many warnings show more context than before.
- Add-Ons: A
shallowCompareadd-on has been added as a migration path forPureRenderMixinin ES6 classes.- Add-Ons:
CSSTransitionGroupcan now use custom class names instead of appending-enter-activeor similar to the transition name.New helpful warnings
- React DOM now warns you when nesting HTML elements invalidly, which helps you avoid surprising errors during updates.
- Passing
document.bodydirectly as the container toReactDOM.rendernow gives a warning as doing so can cause problems with browser extensions that modify the DOM.- Using multiple instances of React together is not supported, so we now warn when we detect this case to help you avoid running into the resulting problems.
... (truncated)
3603d45 v0.14.0693dd35 Update to fbjs@0.34a4174b 0.14.0-rc1c04d02e Add warnings to React module52b4c9e Upgrade to fbjs, fbjs-scripts @ 0.2b38509c Merge pull request https://github.com/facebook/flipper/issues/4540 from scottburch/ie8-fixecb34de Upgrade ESLint, fix code3f6bca7 0.14.0-beta35f01a90 Update addons.js1da2b29 added suggested comment to get file to pass es-lintThis version was pushed to npm by gnoff, a new releaser for react-refresh since your current version.