{"commit":{"authorEmail":"ben@benalpert.com","authoredAt":"2015-10-07T09:46:44-07:00","subject":"Merge pull request #5072 from spicyj\/14blog","authorName":"Ben Alpert","revision":"55cab74312c54e88252594069671c85acd5a90ba","shortRevision":"55cab74312"},"patch":"diff --git a\/docs\/_posts\/2015-09-10-react-v0.14-rc1.md b\/docs\/_posts\/2015-09-10-react-v0.14-rc1.md\nindex 187bc36793..a1ac0ef44e 100644\n--- a\/docs\/_posts\/2015-09-10-react-v0.14-rc1.md\n+++ b\/docs\/_posts\/2015-09-10-react-v0.14-rc1.md\n@@ -28,7 +28,7 @@ If you can’t use `npm` yet, we also provide pre-built browser builds for your\n Dev build with warnings: \n Minified build for production: \n \n-These builds are also available in the `react` and `react-dom` packages on bower.\n+These builds are also available in the `react` package on bower.\n \n ## Changelog\n \ndiff --git a\/docs\/_posts\/2015-10-07-react-v0.14.md b\/docs\/_posts\/2015-10-07-react-v0.14.md\nnew file mode 100644\nindex 0000000000..c30f1d0c22\n--- \/dev\/null\n+++ b\/docs\/_posts\/2015-10-07-react-v0.14.md\n@@ -0,0 +1,201 @@\n+---\n+title: \"React v0.14\"\n+author: spicyj\n+---\n+\n+We’re happy to announce the release of React 0.14 today! This release has a few major changes, primarily designed to simplify the code you write every day and to better support environments like React Native.\n+\n+If you tried the release candidate, thank you – your support is invaluable and we've fixed a few bugs that you reported.\n+\n+As with all of our releases, we consider this version to be stable enough to use in production and recommend that you upgrade in order to take advantage of our latest improvements.\n+\n+## Upgrade Guide\n+\n+Like always, we have a few breaking changes in this release. We know changes can be painful (the Facebook codebase has over 15,000 React components), so we always try to make changes gradually in order to minimize the pain.\n+\n+If your code is free of warnings when running under React 0.13, upgrading should be easy. We have two new small breaking changes that didn't give a warning in 0.13 (see below). Every new change in 0.14, including the major changes below, is introduced with a runtime warning and will work as before until 0.15, so you don't have to worry about your app breaking with this upgrade.\n+\n+See the changelog below for more details.\n+\n+## Installation\n+\n+We recommend using React from `npm` and using a tool like browserify or webpack to build your code into a single bundle. To install the two packages:\n+\n+* `npm install --save react react-dom`\n+\n+Remember that by default, React runs extra checks and provides helpful warnings in development mode. When deploying your app, set the `NODE_ENV` environment variable to `production` to use the production build of React which does not include the development warnings and runs significantly faster.\n+\n+If you can’t use `npm` yet, we provide pre-built browser builds for your convenience, which are also available in the `react` package on bower.\n+\n+* **React** \n+ Dev build with warnings: \n+ Minified build for production: \n+* **React with Add-Ons** \n+ Dev build with warnings: \n+ Minified build for production: \n+* **React DOM** (include React in the page before React DOM) \n+ Dev build with warnings: \n+ Minified build for production: \n+\n+## Changelog\n+\n+### Major changes\n+\n+- #### Two Packages: React and React DOM\n+\n+ As we look at packages like [react-native](https:\/\/github.com\/facebook\/react-native), [react-art](https:\/\/github.com\/reactjs\/react-art), [react-canvas](https:\/\/github.com\/Flipboard\/react-canvas), and [react-three](https:\/\/github.com\/Izzimach\/react-three), it has become clear that the beauty and essence of React has nothing to do with browsers or the DOM.\n+\n+ To make this more clear and to make it easier to build more environments that React can render to, we’re splitting the main `react` package into two: `react` and `react-dom`. **This paves the way to writing components that can be shared between the web version of React and React Native.** We don’t expect all the code in an app to be shared, but we want to be able to share the components that do behave the same across platforms.\n+\n+ The `react` package contains `React.createElement`, `.createClass`, `.Component`, `.PropTypes`, `.Children`, and the other helpers related to elements and component classes. We think of these as the [_isomorphic_](http:\/\/nerds.airbnb.com\/isomorphic-javascript-future-web-apps\/) or [_universal_](https:\/\/medium.com\/@mjackson\/universal-javascript-4761051b7ae9) helpers that you need to build components.\n+\n+ The `react-dom` package has `ReactDOM.render`, `.unmountComponentAtNode`, and `.findDOMNode`. In `react-dom\/server` we have server-side rendering support with `ReactDOMServer.renderToString` and `.renderToStaticMarkup`.\n+\n+ ```js\n+ var React = require('react');\n+ var ReactDOM = require('react-dom');\n+\n+ var MyComponent = React.createClass({\n+ render: function() {\n+ return

Hello World<\/div>;\n+ }\n+ });\n+\n+ ReactDOM.render(, node);\n+ ```\n+\n+ The old names will continue to work with a warning until 0.15 is released, and we’ve published the [automated codemod script](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-codemod\/README.md) we used at Facebook to help you with this transition.\n+\n+ The add-ons have moved to separate packages as well:\n+ - `react-addons-clone-with-props`\n+ - `react-addons-create-fragment`\n+ - `react-addons-css-transition-group`\n+ - `react-addons-linked-state-mixin`\n+ - `react-addons-perf`\n+ - `react-addons-pure-render-mixin`\n+ - `react-addons-shallow-compare`\n+ - `react-addons-test-utils`\n+ - `react-addons-transition-group`\n+ - `react-addons-update`\n+ - `ReactDOM.unstable_batchedUpdates` in `react-dom`.\n+\n+ For now, please use matching versions of `react` and `react-dom` (and the add-ons, if you use them) in your apps to avoid versioning problems.\n+\n+- #### DOM node refs\n+\n+ The other big change we’re making in this release is exposing refs to DOM components as the DOM node itself. That means: we looked at what you can do with a `ref` to a React DOM component and realized that the only useful thing you can do with it is call `this.refs.giraffe.getDOMNode()` to get the underlying DOM node. Starting with this release, `this.refs.giraffe` _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.**\n+\n+ ```js\n+ var Zoo = React.createClass({\n+ render: function() {\n+ return

Giraffe name: <\/div>;\n+ },\n+ showName: function() {\n+ \/\/ Previously: var input = this.refs.giraffe.getDOMNode();\n+ var input = this.refs.giraffe;\n+ alert(input.value);\n+ }\n+ });\n+ ```\n+\n+ This change also applies to the return result of `ReactDOM.render` when passing a DOM node as the top component. As with refs, this change does not affect custom components.\n+ \n+ With this change, we’re deprecating `.getDOMNode()` and replacing it with `ReactDOM.findDOMNode` (see below). If your components are currently using `.getDOMNode()`, they will continue to work with a warning until 0.15.\n+\n+- #### Stateless functional components\n+\n+ In idiomatic React code, most of the components you write will be stateless, simply composing other components. We’re introducing a new, simpler syntax for these components where you can take `props` as an argument and return the element you want to render:\n+\n+ ```js\n+ \/\/ A functional component using an ES2015 (ES6) arrow function:\n+ var Aquarium = (props) => {\n+ var fish = getFish(props.species);\n+ return {fish}<\/Tank>;\n+ };\n+\n+ \/\/ Or with destructuring and an implicit return, simply:\n+ var Aquarium = ({species}) => (\n+ \n+ {getFish(species)}\n+ <\/Tank>\n+ );\n+\n+ \/\/ Then use: \n+ ```\n+\n+ These components behave just like a React class with only a `render` method defined. Since no component instance is created for a functional component, any `ref` added to one will evaluate to `null`. Functional components do not have lifecycle methods, but you can set `.propTypes` and `.defaultProps` as properties on the function.\n+ \n+ This pattern is designed to encourage the creation of these simple components that should comprise large portions of your apps. In the future, we’ll also be able to make performance optimizations specific to these components by avoiding unnecessary checks and memory allocations.\n+\n+- #### Deprecation of react-tools\n+\n+ The `react-tools` package and `JSXTransformer.js` browser file [have been deprecated](\/react\/blog\/2015\/06\/12\/deprecating-jstransform-and-react-tools.html). You can continue using version `0.13.3` of both, but we no longer support them and recommend migrating to [Babel](http:\/\/babeljs.io\/), which has built-in support for React and JSX.\n+\n+- #### Compiler optimizations\n+\n+ React now supports two compiler optimizations that can be enabled in Babel 5.8.23 and newer. Both of these transforms **should be enabled only in production** (e.g., just before minifying your code) because although they improve runtime performance, they make warning messages more cryptic and skip important checks that happen in development mode, including propTypes.\n+\n+ **Inlining React elements:** The `optimisation.react.inlineElements` transform converts JSX elements to object literals like `{type: 'div', props: ...}` instead of calls to `React.createElement`.\n+\n+ **Constant hoisting for React elements:** The `optimisation.react.constantElements` transform hoists element creation to the top level for subtrees that are fully static, which reduces calls to `React.createElement` and the resulting allocations. More importantly, it tells React that the subtree hasn’t changed so React can completely skip it when reconciling.\n+\n+\n+### Breaking changes\n+\n+In almost all cases, we change our APIs gradually and warn for at least one release to give you time to clean up your code. These two breaking changes did not have a warning in 0.13 but should be easy to find and clean up:\n+\n+- `React.initializeTouchEvents` is no longer necessary and has been removed completely. Touch events now work automatically.\n+- Add-Ons: Due to the DOM node refs change mentioned above, `TestUtils.findAllInRenderedTree` and related helpers are no longer able to take a DOM component, only a custom component.\n+\n+These three breaking changes had a warning in 0.13, so you shouldn’t have to do anything if your code is already free of warnings:\n+\n+- The `props` object is now frozen, so mutating props after creating a component element is no longer supported. In most cases, [`React.cloneElement`](\/react\/docs\/top-level-api.html#react.cloneelement) should be used instead. This change makes your components easier to reason about and enables the compiler optimizations mentioned above.\n+- Plain objects are no longer supported as React children; arrays should be used instead. You can use the [`createFragment`](\/react\/docs\/create-fragment.html) helper to migrate, which now returns an array.\n+- Add-Ons: `classSet` has been removed. Use [classnames](https:\/\/github.com\/JedWatson\/classnames) instead.\n+\n+### New deprecations, introduced with a warning\n+\n+Each of these changes will continue to work as before with a new warning until the release of 0.15 so you can upgrade your code gradually.\n+\n+- Due to the DOM node refs change mentioned above, `this.getDOMNode()` is now deprecated and `ReactDOM.findDOMNode(this)` can be used instead. Note that in most cases, calling `findDOMNode` is now unnecessary – see the example above in the “DOM node refs” section.\n+\n+ With each returned DOM node, we've added a `getDOMNode` method for backwards compatibility that will work with a warning until 0.15. If you have a large codebase, you can use our [automated codemod script](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-codemod\/README.md) to change your code automatically.\n+\n+- `setProps` and `replaceProps` are now deprecated. Instead, call ReactDOM.render again at the top level with the new props.\n+- ES6 component classes must now extend `React.Component` in order to enable stateless function components. The [ES3 module pattern](\/react\/blog\/2015\/01\/27\/react-v0.13.0-beta-1.html#other-languages) will continue to work.\n+- Reusing and mutating a `style` object between renders has been deprecated. This mirrors our change to freeze the `props` object.\n+- Add-Ons: `cloneWithProps` is now deprecated. Use [`React.cloneElement`](\/react\/docs\/top-level-api.html#react.cloneelement) instead (unlike `cloneWithProps`, `cloneElement` does not merge `className` or `style` automatically; you can merge them manually if needed).\n+- Add-Ons: To improve reliability, `CSSTransitionGroup` will no longer listen to transition events. Instead, you should specify transition durations manually using props such as `transitionEnterTimeout={500}`.\n+\n+### Notable enhancements\n+\n+- Added `React.Children.toArray` which 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 your `render` methods, especially if you want to reorder or slice `this.props.children` before passing it down. In addition, `React.Children.map` now returns plain arrays too.\n+- React uses `console.error` instead of `console.warn` for 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.)\n+- Previously, including untrusted objects as React children [could result in an XSS security vulnerability](http:\/\/danlec.com\/blog\/xss-via-a-spoofed-react-element). 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](https:\/\/github.com\/facebook\/react\/pull\/4832) with a specific [ES2015 (ES6) `Symbol`] (http:\/\/www.2ality.com\/2014\/12\/es6-symbols.html) in 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 a `Symbol` polyfill for older browsers, such as the one included by [Babel’s polyfill](http:\/\/babeljs.io\/docs\/usage\/polyfill\/).\n+- When possible, React DOM now generates XHTML-compatible markup.\n+- 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`.\n+- React DOM now supports these SVG attributes, which render into namespaced attributes: `xlinkActuate`, `xlinkArcrole`, `xlinkHref`, `xlinkRole`, `xlinkShow`, `xlinkTitle`, `xlinkType`, `xmlBase`, `xmlLang`, `xmlSpace`.\n+- The `image` SVG tag is now supported by React DOM.\n+- In React DOM, arbitrary attributes are supported on custom elements (those with a hyphen in the tag name or an `is=\"...\"` attribute).\n+- React DOM now supports these media events on `audio` and `video` tags: `onAbort`, `onCanPlay`, `onCanPlayThrough`, `onDurationChange`, `onEmptied`, `onEncrypted`, `onEnded`, `onError`, `onLoadedData`, `onLoadedMetadata`, `onLoadStart`, `onPause`, `onPlay`, `onPlaying`, `onProgress`, `onRateChange`, `onSeeked`, `onSeeking`, `onStalled`, `onSuspend`, `onTimeUpdate`, `onVolumeChange`, `onWaiting`.\n+- Many small performance improvements have been made.\n+- Many warnings show more context than before.\n+- Add-Ons: A [`shallowCompare`](https:\/\/github.com\/facebook\/react\/pull\/3355) add-on has been added as a migration path for `PureRenderMixin` in ES6 classes.\n+- Add-Ons: `CSSTransitionGroup` can now use [custom class names](https:\/\/github.com\/facebook\/react\/blob\/48942b85\/docs\/docs\/10.1-animation.md#custom-classes) instead of appending `-enter-active` or similar to the transition name.\n+\n+### New helpful warnings\n+\n+- React DOM now warns you when nesting HTML elements invalidly, which helps you avoid surprising errors during updates.\n+- Passing `document.body` directly as the container to `ReactDOM.render` now gives a warning as doing so can cause problems with browser extensions that modify the DOM.\n+- 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.\n+\n+### Notable bug fixes\n+\n+- Click events are handled by React DOM more reliably in mobile browsers, particularly in Mobile Safari.\n+- SVG elements are created with the correct namespace in more cases.\n+- React DOM now renders `

dillon1000/react

Files changed