6f1417c849
Summary: Copy of #5760 reverted merge. We need to preserve history of docs changes on the webserver. The goal is to allow users to browse outdated versions of docs. To make things simple all websites will be released to https://facebook.github.io/react-native/releases/version/XX folder when there is a branch cut. I switched from Travis CI to Cirle CI because it works faster and I am more familiar with it. How it works: 1. If code is pushed to `master` branch then CI will build a fresh version of docs and put it in https://github.com/facebook/react-native/tree/gh-pages/releases/next folder. Github will serve this website from https://facebook.github.io/react-native/releases/version/next URL. All relative URLs will work within that website 2. If code is pushed to `0.20-stable` branch then CI will build a fresh version of docs and put it in https://github.com/facebook/react-native/tree/gh-pages/releases/0.20 folder. Github will serve this website from https://facebook.github.io/react-native/releases/v Closes https://github.com/facebook/react-native/pull/5873 Reviewed By: svcscm Differential Revision: D2926901 Pulled By: androidtrunkagent fb-gh-sync-id: 16aea430bac815933d9c603f03921cc6353906f1 shipit-source-id: 16aea430bac815933d9c603f03921cc6353906f1
2.9 KiB
| id | title | layout | category | permalink | next |
|---|---|---|---|---|---|
| upgrading | Upgrading | docs | Guides | docs/upgrading.html | platform-specific-code |
Upgrading to new versions of React Native will give you access to more APIs, views, developer tools and other goodies. Because React Native projects are essentially made up of an Android project, an iOS project and a JavaScript project, all combined under an npm package, upgrading can be rather tricky. But we try to make it easy for you. Here's what you need to do to upgrade from an older version of React Native:
1. Upgrade the react-native dependency
Note the latest version of the react-native npm package from here (or use npm info react-native to check):
Now install that version of react-native in your project with npm install --save. For example, to upgrade to the version 0.18, in a terminal run:
$ npm install --save react-native@0.18
2. Upgrade your project templates
The new npm package will likely contain updates to the files that are normally generated when you
run react-native init, like the iOS and the Android sub-projects. To get these latest changes,
run this in a terminal:
$ react-native upgrade
This will check your files against the latest template and perform the following:
- If there is a new file in the template, it is simply created.
- If a file in the template is identical to your file, it is skipped.
- If a file is different in your project than the template, you will be prompted; you have options
to view a diff between your file and the template file, keep your file or overwrite it with the
template version. If you are unsure, press
hto get a list of possible commands.
Manual Upgrades
Xcode project format is pretty complex and sometimes it's tricky to upgrade and merge new changes.
From 0.13 to 0.14
The major change in this version happened to the CLI (see changelog) and static images (see docs). To use the new asset system in existing Xcode project, do the following:
Add new "Run Script" step to your project's build phases:
Set the script to
../node_modules/react-native/packager/react-native-xcode.sh
Move main.jsbundle to Trash (it will be generated automatically by Xcode using the script above)
If you installed Node via nvm, you might experience "react-native: command not found". See issues/3974 for workaround and pull/4015 for the fix.