Thank you for using and supporting rn-diff!
This repository exposes an untouched React Native app generated with the CLI
react-native init RnDiffApp and upgraded with the CLI
after each version of React Native.
A dedicated branch per version makes changes very easy to watch. For example:
- https://github.com/ncuillery/rn-diff/compare/rn-0.28.0...rn-0.29.0 (Change in Android template)
- https://github.com/ncuillery/rn-diff/compare/rn-0.29.0...rn-0.29.2 (no change)
(minor change in
See table below for the complete list.
This repository can also be used to upgrade React Native with a git-like interface which is
faster and easier than running the
react-native upgrade command.
See USAGE.md for details.
Note that the diff stat (last column) doesn't take the
package.json into account (it
doesn't have to: the
package.json must be updated by hand before upgrading React Native).
Why this repository ?
After an upgrade of React Native on your project, according to the
you have to run the CLI command
react-native upgrade to upgrade the files in the
android directories with the new template.
This process can be painful if you had made some changes in these files, especially
those which are not meant to be read by human (the goddam
It inevitably happens by using 3rd-party librairies or changing native
stuff (device orientation, splash screen, etc.).
The CLI detects any file changed by user, shows the diff and asks user if it must be override or keep untouched.
By knowing the real changes due to the React Native upgrade, you can easily
know which option is the best for you. For example, from
the 0.28.0 to the 0.29.0
the changes in the
android files are huge so it may be easier for you to override
and reapplied your changes (relinking your 3-rd parties, etc.) BUT if you
look at the
project.pbxproj, there is only one flag added, so the best decision
for this file is to keep it untouched and report the flag yourself on the right
The version 0.56.0 and 0.57.0 changed a lot about the packager and babel. Because the upgrade was not easy or successful, I created a new project over the existing, and got the diff that way.
The version jumps from 0.55.4 to 0.57.0.
The version 0.49.0 introduces a unified entry-point:
index.android.js were replaced by
rn-diff doesn't show that change because the concerned files are skipped during the upgrade process.
That change is referenced in some native files though, so you have to follow the update guide in the 0.49.0 release notes.
Due to an issue with the Yeoman generator used before 0.39.0 (the
file was never updated), the diff of this file
from 0.38.0 to 0.39.0
is irrelevant. It shows the diff from 0.23.0 to 0.39.0 because the RnDiffApp has been
generated with 0.23.0. You'll probably have less changes on this file when upgrading from 0.38.0 to
0.39.0 depending of the version your app has been generated with. See
#8 for details.
Why starting from 0.23.0 ?
The starting point is the generation of an app with the CLI tool. I've started from the first
react-native since the release 0.2.0 the
react-native-cli (March 2016), the first
to seem mature and stable (3 months after the previous release).
How did you do this ?
I initialized the 3 or 4 first commits manually to see where was it going. Then I automated things with this script.
How can I contribute ?
Unfortunately you can't ;). Correct me if I'm wrong but due to the particular structure of the branch tree, it's impossible to collaborate in the classic way (Pull Request on a non-existing branch).
Nevertheless, when a new version of React Native is released, I'll have to be prompt to provide the new diff. I guess having 3 or 4 collaborators on this project will help in the future. If you're interested, please open an issue to discuss.
Of course, the above doesn't concern suggesting changes on the
master branch (script or
README.md). Pull Requests are highly welcome !