This process started with WebView with great results.Ġ.59 extracts some more components and APIs and marks them as deprecated. This is why non-core components into new community run repositories. It makes it hard for non-core parts of the codebase to be approachable to new contributors. The React Native repository is very large and complex. This version marks the start of the Lean Core effort. You can read more about it on the React Native website. This is an opt-in feature and they are looking for feedback. It optimises the start up time of your app by allowing the Metro bundler to identify modules which can by lazily loaded.

Inline Requiresįacebook is bringing some of their performance optimisations to the community. Before then, you will need to upgrade to at least React Native 0.59 to be able to make changes to your app on Android. It also enables 64-bit support on Android, which will be a requirement for apps on the Google Play Store from 1st August 2019. The upgraded library includes performance increases and some features which were previously polyfilled. Previous versions of React Native bundled a very old library on Android. On iOS, it uses a system provided framework.

On Android, the JavascriptCore library used to run your JS code is bundled within your app. Android JavascriptCore Upgrade & 64-bit SupportĪnother large change is the upgrade to JavascriptCore for Android. You can read more about hooks on the React website. They are an opt-in feature and will work side-by-side with your current code, so you can adopt it gradually. Hooks let you re-use state logic between components, without resorting to classes. The most noticeable change to developers is the addition of Hooks. Take a look at those for the full details. This is a summary of the React Native blog post and the full changelog. Let‘s take a look at what‘s new in this version.

React native android studio gradle