Upgrading react-native 0.9 to 0.10
Breaking0.9.0 → 0.10.1Breaking4New14Fixed17Other5
BreakingUpgrade verdict
4 breaking changes.
In plain terms
- AnimationExperimental has been removed: Use the JS Animated API or react-motion instead.
- NSNumber parameters must be marked nonnull: Native bridge methods that take NSNumber values must annotate them using the Objective-C nonnull keyword.
- customDirectEventTypes should return an array rather than a dictionary: see for details if you depend on this in any of your native component libraries.
- RCTViewNodeProtocol is now RCTComponent: this was done as part of a refactoring of RCTUIManager, similar to above, see for details if you depend on RCTViewNodeProtocol in any of your native…
Must act Top 3 of 4 that need code or config changes
Adds regenerator 0.8.36, stacktrace-parser 0.1.2.
Installs 408 packages in all (was 407).
What you must change
Breaking4
AnimationExperimental has been removed: Use the JS Animated API or react-motion instead.
NSNumber parameters must be marked nonnull: Native bridge methods that take NSNumber values must annotate them using the Objective-C nonnull keyword.
NSNumbernonnullcustomDirectEventTypes should return an array rather than a dictionary: see for details if you depend on this in any of your native component libraries.
RCTViewNodeProtocol is now RCTComponent: this was done as part of a refactoring of RCTUIManager, similar to above, see for details if you depend on RCTViewNodeProtocol in any of your native…
RCTViewNodeProtocol