diff --git a/releases/next/docs/integration-with-existing-apps.html b/releases/next/docs/integration-with-existing-apps.html index 48b399f8335..de7a9cc3231 100644 --- a/releases/next/docs/integration-with-existing-apps.html +++ b/releases/next/docs/integration-with-existing-apps.html @@ -97,7 +97,7 @@ "scripts": { "start": "node node_modules/react-native/local-cli/cli.js start" } -}

Next, you will install the react and react-native packages. Open a terminal or command prompt, then navigate to the root directory for your project and type the following commands:

$ npm install --save react react-native

This will create a new /node_modules folder in your project's root directory. This folder stores all the JavaScript dependencies required to build your project.

+}

Next, you will install the react and react-native packages. Open a terminal or command prompt, then navigate to the root directory for your project and type the following commands:

$ npm install --save react@16.0.0-beta.5 react-native

Make sure you use the same React version as specified in the React Native package.json for your release. This will only be necessary as long as React Native depends on a pre-release version of React.

This will create a new /node_modules folder in your project's root directory. This folder stores all the JavaScript dependencies required to build your project.

3. Install CocoaPods #

CocoaPods is a package management tool for iOS and macOS development. We use it to add the actual React Native framework code locally into your current project.

We recommend installing CocoaPods using Homebrew.

$ brew install cocoapods

It is technically possible not to use CocoaPods, but that would require manual library and linker additions that would overly complicate this process.

@@ -282,6 +282,7 @@ $ react-native runGitHub.

Adding React Native to your app #

Configuring maven #

Add the React Native dependency to your app's build.gradle file:

dependencies { + compile 'com.android.support:appcompat-v7:23.0.1' ... compile "com.facebook.react:react-native:+" // From node_modules. }

If you want to ensure that you are always using a specific React Native version in your native build, replace + with an actual React Native version you've downloaded from npm.

Add an entry for the local React Native maven directory to build.gradle. Be sure to add it to the "allprojects" block:

allprojects { @@ -289,7 +290,7 @@ $ react-native run... maven { // All of React Native (JS, Android binaries) is installed from npm - url "$rootDir/node_modules/react-native/android" + url "$rootDir/../node_modules/react-native/android" } } ... @@ -392,7 +393,7 @@ AppRegistry. super.onDestroy(); if (mReactInstanceManager != null) { - mReactInstanceManager.onHostDestroy(); + mReactInstanceManager.onHostDestroy(this); } }

We also need to pass back button events to React Native:

@Override public void onBackPressed() { diff --git a/versions.html b/versions.html index 8706bbf8af2..04d29365853 100644 --- a/versions.html +++ b/versions.html @@ -1,4 +1,4 @@ -React Native Versions
React Native0.48

React Native Versions

React Native follows a monthly release train. Every month, a new branch created off master enters the Release Candidate phase, and the previous Release Candidate branch is released and considered stable.

If you have an existing project that uses React Native, read the release notes to learn about new features and fixes. You can follow our guide to upgrade your app to the latest version.

Current version (Stable)

0.48DocumentationRelease Notes

This is the version that is configured automatically when you create a new project using react-native init.

Pre-release versions

masterDocumentation
0.49-RCDocumentationRelease Notes

To see what changes are coming and provide better feedback to React Native contributors, use the latest release candidate when possible. By the time a release candidate is released, the changes it contains will have been shipped in production Facebook apps for over two weeks.

Past versions

0.47DocumentationRelease Notes
0.46DocumentationRelease Notes
0.45DocumentationRelease Notes
0.44DocumentationRelease Notes
0.43DocumentationRelease Notes
0.42DocumentationRelease Notes
0.41DocumentationRelease Notes
0.40DocumentationRelease Notes
0.39DocumentationRelease Notes
0.38DocumentationRelease Notes
0.37DocumentationRelease Notes
0.36DocumentationRelease Notes
0.35DocumentationRelease Notes
0.34DocumentationRelease Notes
0.33DocumentationRelease Notes
0.32DocumentationRelease Notes
0.31DocumentationRelease Notes
0.30DocumentationRelease Notes
0.29DocumentationRelease Notes
0.28DocumentationRelease Notes
0.27DocumentationRelease Notes
0.26DocumentationRelease Notes
0.25DocumentationRelease Notes
0.24DocumentationRelease Notes
0.23DocumentationRelease Notes
0.22DocumentationRelease Notes
0.21DocumentationRelease Notes
0.20DocumentationRelease Notes
0.19DocumentationRelease Notes
0.18DocumentationRelease Notes

You can find past versions of React Native on GitHub. The release notes can be useful if you would like to learn when a specific feature or fix was released.

You can also view the docs for a particular version of React Native by clicking on the Docs link next to the release in this page. You can come back to this page and switch the version of the docs you're reading at any time by clicking on the version number at the top of the page.

React Nativenext

React Native Versions

React Native follows a monthly release train. Every month, a new branch created off master enters the Release Candidate phase, and the previous Release Candidate branch is released and considered stable.

If you have an existing project that uses React Native, read the release notes to learn about new features and fixes. You can follow our guide to upgrade your app to the latest version.

Current version (Stable)

0.48DocumentationRelease Notes

This is the version that is configured automatically when you create a new project using react-native init.

Pre-release versions

masterDocumentation
0.49-RCDocumentationRelease Notes

To see what changes are coming and provide better feedback to React Native contributors, use the latest release candidate when possible. By the time a release candidate is released, the changes it contains will have been shipped in production Facebook apps for over two weeks.

Past versions

0.47DocumentationRelease Notes
0.46DocumentationRelease Notes
0.45DocumentationRelease Notes
0.44DocumentationRelease Notes
0.43DocumentationRelease Notes
0.42DocumentationRelease Notes
0.41DocumentationRelease Notes
0.40DocumentationRelease Notes
0.39DocumentationRelease Notes
0.38DocumentationRelease Notes
0.37DocumentationRelease Notes
0.36DocumentationRelease Notes
0.35DocumentationRelease Notes
0.34DocumentationRelease Notes
0.33DocumentationRelease Notes
0.32DocumentationRelease Notes
0.31DocumentationRelease Notes
0.30DocumentationRelease Notes
0.29DocumentationRelease Notes
0.28DocumentationRelease Notes
0.27DocumentationRelease Notes
0.26DocumentationRelease Notes
0.25DocumentationRelease Notes
0.24DocumentationRelease Notes
0.23DocumentationRelease Notes
0.22DocumentationRelease Notes
0.21DocumentationRelease Notes
0.20DocumentationRelease Notes
0.19DocumentationRelease Notes
0.18DocumentationRelease Notes

You can find past versions of React Native on GitHub. The release notes can be useful if you would like to learn when a specific feature or fix was released.

You can also view the docs for a particular version of React Native by clicking on the Docs link next to the release in this page. You can come back to this page and switch the version of the docs you're reading at any time by clicking on the version number at the top of the page.

\ No newline at end of file