We’re happy to announce the availability of React v0.12! After over a week of baking as the release candidate, we uncovered and fixed a few small issues. Thanks to all of you who upgraded and gave us feedback!
\nWe have talked a lot about some of the bigger changes in this release. We introduced new terminology and changed APIs to clean up and simplify some of the concepts of React. We also made several changes to JSX and deprecated a few functions. We won’t go into depth about these changes again but we encourage you to read up on these changes in the linked posts. We’ll summarize these changes and discuss some of the other changes and how they may impact you below. As always, a full changelog is also included below.
\nThe release is available for download:
\nWe’ve also published version 0.12.0 of the react and react-tools packages on npm and the react package on bower.
v0.12 is bringing about some new terminology. We introduced this 2 weeks ago and we’ve also documented it in a new section of the documentation. As a part of this, we also corrected many of our top-level APIs to align with the terminology. Component has been removed from all of our React.render* methods. While at one point the argument you passed to these functions was called a Component, it no longer is. You are passing ReactElements. To align with render methods in your component classes, we decided to keep the top-level functions short and sweet. React.renderComponent is now React.render.
We also corrected some other misnomers. React.isValidComponent actually determines if the argument is a ReactElement, so it has been renamed to React.isValidElement. In the same vein, React.PropTypes.component is now React.PropTypes.element and React.PropTypes.renderable is now React.PropTypes.node.
The old methods will still work but will warn upon first use. They will be removed in v0.13.
\nWe talked more in depth about these before, so here are the highlights.
\n/** @jsx React.DOM */!<Component/> now becomes React.createElement(Component)React.DOM, instead we pass the tag name directly. <div/> becomes React.createElement('div')__internals For months we’ve gotten complaints about the React DevTools message. It shouldn’t have logged the up-sell message when you were already using the DevTools. Unfortunately this was because the way we implemented these tools resulted in the DevTools knowing about React, but not the reverse. We finally gave this some attention and enabled React to know if the DevTools are installed. We released an update to the devtools several weeks ago making this possible. Extensions in Chrome should auto-update so you probably already have the update installed!
\nAs a result of this update, we no longer need to expose several internal modules to the world. If you were taking advantage of this implementation detail, your code will break. React.__internals is no more.
We updated the license on React to the BSD 3-Clause license with an explicit patent grant. Previously we used the Apache 2 license. These licenses are very similar and our extra patent grant is equivalent to the grant provided in the Apache license. You can still use React with the confidence that we have granted the use of any patents covering it. This brings us in line with the same licensing we use across the majority of our open source projects at Facebook.
\nYou can read the full text of the LICENSE and PATENTS files on GitHub.
key and ref moved off props object, now accessible on the element directlyReact.__internals is removed - it was exposed for DevTools which no longer needs accessReact.createFactory first. This is handled for you when using JSX.{...}) introduced to deprecate this.transferPropsToacceptCharset, classID, manifestReact.renderComponent —> React.renderReact.renderComponentToString —> React.renderToStringReact.renderComponentToStaticMarkup —> React.renderToStaticMarkupReact.isValidComponent —> React.isValidElementReact.PropTypes.component —> React.PropTypes.elementReact.PropTypes.renderable —> React.PropTypes.nodeReact.isValidClassinstance.transferPropsTofalse from event handlers to preventDefaultReact.createFactorykey={null} to assign implicit keysevent.getModifierState as case sensitiveevent.charCodeFixed support for some HTML attributes:
\nlist updates correctly nowscrollLeft, scrollTop removed, these should not be specified as propsReact.addons.batchedUpdates added to API for hooking into update cycleReact.addons.update uses assign instead of copyProperties which does hasOwnProperty checks. Properties on prototypes will no longer be updated correctly.@jsx React.DOM no longer required{...}) operator introduced to allow easier use of props