Skip to content

Upgrading react-native 0.6 to 0.7

Breaking0.6.0 → 0.7.1Breaking5Deprecated1New11Changed4Fixed5Other1

Full comparisonBack to react-native
BreakingUpgrade verdict

5 breaking changes.

In plain terms
  • If you nest navigators, the child no longer forwards navigation calls to the parent automatically; you must call the parent yourself.
  • Network requests that receive non-text responses will now fail with an error.
  • Module paths are now resolved the way Node resolves them, so specify paths as you would in Node when unsure.
  • Modules can no longer be required by their @providesModule name across packages; require them by package name instead.
Must act Top 4 of 6 that need code or config changes

Adds babel-core ^5.6.11, sane ^1.1.2.

Installs 398 packages in all (was 387).

What you must change

Breaking5
Removes contextual navigation from Navigator, so nested Navigators no longer delegate navigation calls to their parent.
Navigatorpushpopreplace
0.7.0-rcGitHub ReleaseSummarizedView source
XHR requests now throw an error when the response is anything other than text.
XMLHttpRequest
0.7.0-rcGitHub ReleaseSummarizedView source
The packager follows Node's require resolution algorithm much more closely.
require
0.7.0-rcGitHub ReleaseSummarizedView source
Scopes the @providesModule directive to each npm package instead of the entire app.
@providesModule
0.7.0-rcGitHub ReleaseSummarizedView source
Requires all require statements for React Native modules to go through the public react-native interface.
requireRCTDeviceEventEmitterNativeModulesDeviceEventEmitterRNKeyboardEventsManager
0.7.0-rcGitHub ReleaseSummarizedView source

Deprecations to plan for

Deprecated1
Deprecates onWillFocus and onDidFocus in favor of navigator event listeners.
onWillFocusonDidFocusaddListenerwillfocusdidfocus
0.7.0-rcGitHub ReleaseSummarizedView source