|
| 1 | +--- |
| 2 | +title: "Preparing for the Future with React Prereleases" |
| 3 | +author: [acdlite] |
| 4 | +--- |
| 5 | + |
| 6 | +To share upcoming changes with our partners in the React ecosystem, we're establishing official prerelease channels. We hope this process will help us make changes to React with confidence, and give developers the opportunity to try out experimental features. |
| 7 | + |
| 8 | +> This post will be most relevant to developers who work on frameworks, libraries, or developer tooling. Developers who use React primarily to build user-facing applications should not need to worry about our prerelease channels. |
| 9 | +
|
| 10 | +React relies on a thriving open source community to file bug reports, open pull requests, and [submit RFCs](https://github.com/reactjs/rfcs). To encourage feedback, we sometimes share special builds of React that include unreleased features. |
| 11 | + |
| 12 | +Because the source of truth for React is our [public GitHub repository](https://github.com/facebook/react), it's always been possible to build a copy of React that includes the latest changes. However it's much easier for developers to install React from npm, so we occasionally publish prerelease builds to the npm registry. A recent example is the 16.7 alpha, which included an early version of the Hooks API. |
| 13 | + |
| 14 | +We would like to make it even easier for developers to test prerelease builds of React, so we're formalizing our process with three separate release channels. |
| 15 | + |
| 16 | +## Release Channels {#release-channels} |
| 17 | + |
| 18 | +> The information in this post is also available on our [Release Channels](/docs/release-channels.html) page. We will update that document whenever there are changes to our release process. |
| 19 | +
|
| 20 | +Each of React's release channels is designed for a distinct use case: |
| 21 | + |
| 22 | +- [**Latest**](#latest-channel) is for stable, semver React releases. It's what you get when you install React from npm. This is the channel you're already using today. **Use this for all user-facing React applications.** |
| 23 | +- [**Next**](#next-channel) tracks the master branch of the React source code repository. Think of these as release candidates for the next minor semver release. Use this for integration testing between React and third party projects. |
| 24 | +- [**Experimental**](#experimental-channel) includes experimental APIs and features that aren't available in the stable releases. These also track the master branch, but with additional feature flags turned on. Use this to try out upcoming features before they are released. |
| 25 | + |
| 26 | +All releases are published to npm, but only Latest uses [semantic versioning](/docs/faq-versioning.html). Prereleases (those in the Next and Experimental channels) have versions generated from a hash of their contents, e.g. `0.0.0-1022ee0ec` for Next and `0.0.0-experimental-1022ee0ec` for Experimental. |
| 27 | + |
| 28 | +**The only officially supported release channel for user-facing applications is Latest**. Next and Experimental releases are provided for testing purposes only, and we provide no guarantees that behavior won't change between releases. They do not follow the semver protocol that we use for releases from Latest. |
| 29 | + |
| 30 | +By publishing prereleases to the same registry that we use for stable releases, we are able to take advantage of the many tools that support the npm workflow, like [unpkg](https://unpkg.com) and [CodeSandbox](https://codesandbox.io). |
| 31 | + |
| 32 | +### Latest Channel {#latest-channel} |
| 33 | + |
| 34 | +Latest is the channel used for stable React releases. It corresponds to the `latest` tag on npm. It is the recommended channel for all React apps that are shipped to real users. |
| 35 | + |
| 36 | +**If you're not sure which channel you should use, it's Latest.** If you're a React developer, this is what you're already using. |
| 37 | + |
| 38 | +You can expect updates to Latest to be extremely stable. Versions follow the semantic versioning scheme. Learn more about our commitment to stability and incremental migration in our [versioning policy](/docs/faq-versioning.html). |
| 39 | + |
| 40 | +### Next Channel {#next-channel} |
| 41 | + |
| 42 | +The Next channel is a prerelease channel that tracks the master branch of the React repository. We use prereleases in the Next channel as release candidates for the Latest channel. You can think of Next as a superset of Latest that is updated more frequently. |
| 43 | + |
| 44 | +The degree of change between the most recent Next release and the most recent Latest release is approximately the same as you would find between two minor semver releases. However, **the Next channel does not conform to semantic versioning.** You should expect occasional breaking changes between successive releases in the Next channel. |
| 45 | + |
| 46 | +**Do not use prereleases in user-facing applications.** |
| 47 | + |
| 48 | +Releases in Next are published with the `next` tag on npm. Versions are generated from a hash of the build's contents, e.g. `0.0.0-1022ee0ec`. |
| 49 | + |
| 50 | +#### Using the Next Channel for Integration Testing {#using-the-next-channel-for-integration-testing} |
| 51 | + |
| 52 | +The Next channel is designed to support integration testing between React and other projects. |
| 53 | + |
| 54 | +All changes to React go through extensive internal testing before they are released to the public. However, there are a myriad of environments and configurations used throughout the React ecosystem, and it's not possible for us to test against every single one. |
| 55 | + |
| 56 | +If you're the author of a third party React framework, library, developer tool, or similar infrastructure-type project, you can help us keep React stable for your users and the entire React community by periodically running your test suite against the most recent changes. If you're interested, follow these steps: |
| 57 | + |
| 58 | +- Set up a cron job using your preferred continuous integration platform. Cron jobs are supported by both [CircleCI](https://circleci.com/docs/2.0/triggers/#scheduled-builds) and [Travis CI](https://docs.travis-ci.com/user/cron-jobs/). |
| 59 | +- In the cron job, update your React packages to the most recent React release in the Next channel, using `next` tag on npm. Using the npm cli: |
| 60 | + |
| 61 | + ``` |
| 62 | + npm update react@next react-dom@next |
| 63 | + ``` |
| 64 | + |
| 65 | + Or yarn: |
| 66 | + |
| 67 | + ``` |
| 68 | + yarn upgrade react@next react-dom@next |
| 69 | + ``` |
| 70 | +- Run your test suite against the updated packages. |
| 71 | +- If everything passes, great! You can expect that your project will work with the next minor React release. |
| 72 | +- If something breaks unexpectedly, please let us know by [filing an issue](https://github.com/facebook/react/issues). |
| 73 | + |
| 74 | +A project that uses this workflow is Next.js. (No pun intended! Seriously!) You can refer to their [CircleCI configuration](https://github.com/zeit/next.js/blob/c0a1c0f93966fe33edd93fb53e5fafb0dcd80a9e/.circleci/config.yml) as an example. |
| 75 | + |
| 76 | +### Experimental Channel {#experimental-channel} |
| 77 | + |
| 78 | +Like Next, the Experimental channel is a prerelease channel that tracks the master branch of the React repository. Unlike Next, Experimental releases include additional features and APIs that are not ready for wider release. |
| 79 | + |
| 80 | +Usually, an update to Next is accompanied by a corresponding update to Experimental. They are based on the same source revision, but are built using a different set of feature flags. |
| 81 | + |
| 82 | +Experimental releases may be significantly different than releases to Next and Latest. **Do not use Experimental releases in user-facing applications.** You should expect frequent breaking changes between releases in the Experimental channel. |
| 83 | + |
| 84 | +Releases in Experimental are published with the `experimental` tag on npm. Versions are generated from a hash of the build's contents, e.g. `0.0.0-experimental-1022ee0ec`. |
| 85 | + |
| 86 | +#### What Goes Into an Experimental Release? {#what-goes-into-an-experimental-release} |
| 87 | + |
| 88 | +Experimental features are ones that are not ready to be released to the wider public, and may change drastically before they are finalized. Some experiments may never be finalized -- the reason we have experiments is to test the viability of proposed changes. |
| 89 | + |
| 90 | +For example, if the Experimental channel had existed when we announced Hooks, we would have released Hooks to the Experimental channel weeks before they were available in Latest. |
| 91 | + |
| 92 | +You may find it valuable to run integration tests against Experimental. This is up to you. However, be advised that Experimental is even less stable than Next. **We do not guarantee any stability between Experimental releases.** |
| 93 | + |
| 94 | +#### How Can I Learn More About Experimental Features? {#how-can-i-learn-more-about-experimental-features} |
| 95 | + |
| 96 | +Experimental features may or may not be documented. Usually, experiments aren't documented until they are close to shipping in Next or Stable. |
| 97 | + |
| 98 | +If a feature is not documented, they may be accompanied by an [RFC](https://github.com/reactjs/rfcs). |
| 99 | + |
| 100 | +We will post to the React blog when we're ready to announce new experiments, but that doesn't mean we will publicize every experiment. |
| 101 | + |
| 102 | +You can always refer to our public GitHub repository's [history](https://github.com/facebook/react/commits/master) for a comprehensive list of changes. |
0 commit comments