The long-awaited 0.56 release of React Native is presently available. This blog entry highlights a portion of the changes introduced in this new release. We additionally need to accept the open door to clarify what has kept us occupied since March.
The breaking changes dilemma, or, “when to release?”
The project is formed by various tools, requiring coordination and consistent help to continue everything working legitimately. Add to this the vibrant open source community that contributes back to the task, and you will get a feeling of the mind-bending scale, all things considered,
With the release of React Native amazing reception, breaking changes must be made with awesome care, and the procedure isn’t as smooth as we’d like. A choice was made to avoid the April and May releases to permit the center group to incorporate and test another arrangement of breaking changes. Dedicated community communication channels were utilized along the best approach to guarantee that the June 2018 (0.56.0) release is as problem free as possible to embrace by the individuals who persistently sat tight for the steady release.
Is 0.56.0 great? No, as each bit of programming out there: however we achieved a point where the tradeoff between “sitting tight for greater stability” versus “testing prompted victories so we can push forward” that we feel prepared to release it. Moreover, we know about a couple of issues that are not tackled in the last 0.56.0 release. Most developers ought to have no issues moving up to 0.56.0. For those that are obstructed by the aforementioned issues, we want to see you around in our discourses and we are anticipating working with you on a solution to these issues.
You should seriously think about 0.56.0 as a fundamental building hinders towards a more steady structure: it will take probably up to 14 days of far-reaching selection before all the edge cases will be sanded off, yet this will prompt a shockingly better July 2018 (0.57.0) release.
The Big Changes
Babel 7
As you may know, the transpiler tool that enables every one of us to utilize the most recent and most prominent highlights of JavaScript, Babel, is moving to v7 soon. Since this new form brings along some vital changes, we felt that now it would be a decent time to redesign, enabling Metro to use on its enhancements.
In the event that you end up stuck in an unfortunate situation with overhauling, it would be ideal if you allude to the documentation segment identified with it.
Modernizing Android bolster
On Android, a significant part of the encompassing tooling has changed. We’ve refreshed to Gradle 3.5, Android SDK 26, Fresco to 1.9.0, and OkHttp to 3.10.0 and even the NDK API focus to API 16. These changes ought to abandon issue and result in quicker forms. All the more critically, it will enable developers to conform to the new Play Store necessities becoming effective one month from now.
Identified with this, we’d jump at the chance to especially say thanks to Dulmandakh for the numerous PRs submitted keeping in mind the end goal to make it possible ð??.
There are some more advances that should be taken toward this path, and you can take after along with the future arranging and discourse of refreshing the Android bolster in the dedicated issue (and aside one for the JSC).
New Node, Xcode, React, and Flow â?? Amazing!
Hub 8 is currently the standard for React Native. It was very being tried as of now, however, we’ve put the two feet forward as Node 6 entered support mode. React was additionally refreshed to 16.4, which carries a huge amount of fixes with it.
We’re dropping help for iOS 8, making iOS 9 the most seasoned iOS form that can be focused on. We don’t predict this being an issue, as any gadget that can run iOS 8, can be moved up to iOS 9. This change enabled us to evacuate seldom utilized code that executed workarounds for more seasoned gadgets running iOS 8.
The constant combination toolchain has been refreshed to utilize Xcode 9.4, guaranteeing that all iOS tests are kept running on the most recent designer tools given by Apple.
We have moved up to Flow 0.75 to utilize the new blunder arrange that numerous devs appreciate. We’ve additionally made composes for some more parts. In case you’re not yet upholding static writing in your task, it would be ideal if you consider utilizing Flow to recognize issues as you code rather than at runtime.
What’s more, a great deal of different things
For example, YellowBox was supplanted with another usage that improves investigating a ton.
For the entire release notes, if it’s not too much trouble reference the full changelog here. Furthermore, make sure to watch out for the redesigning manual for keep away from issues moving to this new form.
A last note: beginning this week, the React Native center group will continue holding month to month gatherings. We’ll try to stay up with the latest with what’s secured, and guarantee to keep your input within reach for future gatherings.
PS: as usual, we’d jump at the chance to remind everybody that React Native is still in 0.x forming in view of the numerous changes as yet experiencing – so recall while redesigning that yes, probably, something may even now crash or be broken. Be helpful towards each other in the issues and while submitting PRs – and make sure to take after the CoC enforced: there’s dependably a human on the opposite side of the screen.
