React Native v0.11.0-rc and v0.10.0 released

Breaking Changes

Rename RCTReachability to RCTNetInfo: for consistency with Android. The device event that is triggered has also been renamed from reachabilityDidChange to networkDidChange.

Internal functions on Animated marked as protected: if you use attach, detach, getAnimatedValue, addChild, removeChild, or getChildren on your Animated components, you will need to update the code to be compatible. This change is in preparation for future optimizations. 059e605

Known Issues

Packager does not support symlinks: Symlinks under node_modules, for example, are ignored (#637)

New Features

Add support for transparent modal backgrounds: toggle this by using the new transparent prop of Modal.

Add support for HSL/HSLA colors

Built-in support for handling Keyboard events: you can now add listeners to DeviceEventEmitter for keyboardWillShow, keyboardDidShow, keyboardWillHide, keyboardDidHide, keyboardWillChangeFrame and keyboardDidChangeFrame. (9aefd6b)

Built-in support for handling status bar change events: you can now add listeners to DeviceEventEmitter for statusBarFrameDidChange and statusBarFrameWillChange events (eg: if you receive a phonecall, the status bar becomes taller - this allows you to respond accordingly).

Touchable handlers now receive event objects:onPressIn etc - these event objects were already initialized so it was just a matter of threading them through.

JavaScript

Use GLOBAL.process instead of overwriting: respect any existing process value hanging off of the global object, and only set the env property of it. a4e6419

iOS

Pass props when creating a view with RCTViewManager: native module authors will understand that previously it was awkward to set initial properties on a view because props were not available in init and there was no guaranteed order that they would be set in. RCTViewManager classes can now implement viewWithProps:props to better control this.

Other

Bug Fixes

Fix TabBarItemIOS image scale: TabBarItemIOS supports setting the scale for base64-encoded images using an optional scale parameter, however this was broken due to the JS code only passing the uri, not the whole source object, to the native side.