blogpost for 0.68 #3041
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,78 @@ | ||
| --- | ||
| title: Announcing React Native 0.68 | ||
| authors: [kelset, shikaSD] | ||
| tags: [announcement, release] | ||
| --- | ||
|
|
||
| # Announcing 0.68 | ||
|
|
||
| Hello everyone! Today we are announcing the 0.68.0 release of React Native, with opt-in to the New React Native Architecture, bug fixes and more. | ||
|
|
||
| ### Sections | ||
|
|
||
| - [Highlights of 0.68](/blog/2022/03/30/version-068#highlights-of-068) | ||
| - [Opting in into the New Architecture](/blog/2022/03/30/version-068#opting-in-into-the-new-architecture) | ||
| - [Website updates](/blog/2022/03/30/version-068#website-updates) | ||
| - [Interested in helping React Native stabilise new releases?](/blog/2022/03/30/version-068#interested-in-helping-react-native-stabilize-new-releases) | ||
|
|
||
| <!--truncate--> | ||
|
|
||
| ## Highlights of 0.68 | ||
|
|
||
| [Andrei Calazans](https://twitter.com/Andrei_Calazans) helped us selecting the most relevant changes that 0.68 brings along: | ||
|
|
||
| ### Breaking changes and version bumps | ||
|
|
||
| This version brings along a few breaking changes: | ||
|
|
||
| - React Native has been updated to Node 16, the latest LTS. Since on CI we test for LTS and the previous LTS, this change means that users are now required to use a version of Node >= 14. | ||
| - Android Gradle Plugin was updated to 7.0.1, enforcing JDK 11 for Android builds, so make sure to upgrade your configurations (we recommend you use the `temurin11` JDK flavor) | ||
| - Removed `fallbackResource` from `RCTBundleURLProvider` API on iOS. | ||
|
There was a problem hiding this comment. Maybe expand on this that its safe to just remove that parameter from the method call without any replacement. |
||
|
|
||
| Tooling has also been updated - here are the main bumps: | ||
|
|
||
| - @react-native-community/cli to 7.0.3 | ||
| - Metro to 0.67 | ||
| - react-devtools-core dependency to 4.23.0 | ||
| - Flipper to 0.125.0 | ||
| - react-native-codegen to 0.0.9 | ||
| - Kotlin to 1.6.10 | ||
| - Soloader to 0.10.3 | ||
| - Gradle to 7.3 | ||
| - Android compile and target SDK to 31 | ||
|
|
||
| Also, thanks to [this commit](https://github.com/facebook/react-native/commit/bd7caa64f5d6ee5ea9484e92c3629c9ce711f73c) by [Nicola Corti](https://github.com/cortinico) the Android Gradle Plugin will download the default version of NDK by itself, so you don’t have to specify and install it separately anymore. | ||
|
|
||
| ### Other improvements | ||
|
|
||
| There are a lot of other changes and fixes landed in this release, but here’s a small selection that you might be interested in: | ||
|
|
||
| - [Gijs Weterings](https://github.com/GijsWeterings) [fixed Forwarding testID to RCTModalHostView](https://github.com/facebook/react-native/commit/5050e7eaa17cb417baf7c20eb5c4406cce6790a5) for easier E2E targeting of Modals. | ||
| - [Liam Jones](https://github.com/liamjones) [fixed an issue](https://github.com/facebook/react-native/commit/9d2df5b8ae9) where calling `console.error` caused the RedBox to appear alongside the LogBox. | ||
| - [Sam Kline](https://github.com/samkline) [fixed the empty blank screen](https://github.com/facebook/react-native/commit/c8d823b9bd9619dfa1f5851af003cc24ba2e8830) after a BundleDownloader failure in dev mode on Android. | ||
| - [Jeffrey Hyer](https://github.com/JeffreyHyer) [fixed an issue](https://github.com/facebook/react-native/commit/9c5e177a79c) where the KeyboardAvoidingView didn't work as expected with the `onLayout` prop. | ||
|
|
||
| If you are interested in the full list of changes, you can read it in the changelog [at the link here](https://github.com/facebook/react-native/blob/main/CHANGELOG.md#0680). | ||
|
|
||
| ### Acknowledgements | ||
|
|
||
| This release includes 614 commits by 68 contributors! Thank you all! | ||
|
|
||
| We wanted to also thank the release testers and supporters who helped us catch regressions before the stable 0.68.0 release: you are incredibly valuable to the success of this release! | ||
|
|
||
| If you, your app or your company is interested in joining the “Release Tester” program, you can [sign up here](https://forms.gle/fPuPE1MZRDGWNqpd6). | ||
|
|
||
| ## Opting in into the New Architecture | ||
|
|
||
| As briefly mentioned above, React Native 0.68 is the first version with opt-in support for the Fabric Renderer and the TurboModule system. This marks a crucial milestone for the rollout of the New React Native Architecture. To help you get up to speed with the changes, we added [the Architecture section](/architecture/overview) to the website, where you can find several in-depth guides about internals of the new systems. | ||
|
|
||
| At the same time, we added the [migration guide](/docs/next/new-architecture-intro) to the documentation and launched [a working group](https://github.com/reactwg/react-native-new-architecture) dedicated to the New Architecture. You can find more information, including how to opt in, in [the previous blog post](/blog/2022/03/15/an-update-on-the-new-architecture-rollout). | ||
|
|
||
| Please note that the New Architecture still needs some fine tuning. Some of the third-party libraries that you depend on might not be migrated yet, and you may encounter issues that we haven’t discovered yet. If you do so, please report them to our [New Architecture Working Group](https://github.com/reactwg/react-native-new-architecture). | ||
|
|
||
| **About React 18:** React 18's new rendering engine is not supported by React Native 0.68, this will happen in a future version. This is because React 18 relies on the New Architecture to benefit from the new capabilities presented in [the React 18 announcement blog post](https://reactjs.org/blog/2022/03/29/react-v18.html). For more information, see the [React Conf keynote here](https://www.youtube.com/watch?v=FZ0cG47msEk&t=1530s). | ||
|
|
||
| ## Website updates | ||
|
|
||
| Along with improvements to the main codebase, with the help of [Simek](https://github.com/Simek), [Megatron4537](https://github.com/Megatron4537) and [slorber](https://github.com/slorber) there have been quite a few improvements landing on the website too! In particular, you will now be able to learn how to contribute to React Native via the new section in the top toolbar. | ||
| Moreover, the “Contributing” section and the new “Architecture” section are now unversioned — there is now only one copy of these sections, rather than one for each React Native version. | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Especially for m1 it makes sense to also mention azul as this is the only one with arm64 which cuts time for android build in half (on my machine).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe temurin is also doing the same: https://github.com/Homebrew/homebrew-cask/blob/e01d3af6f8ea88ebf803ca61e85bbc42dc64aab4/Casks/temurin.rb#L2
I'm not sure the
temurin11formula has been updated to support Mac M1s, but I believe that will be updated as well.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cortinico The cask you linked is for temurin 17 not 11. Temurin 11 does not yet support arm64.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup I've followed up on the other PR. You're right here thanks for clarifying.
Side note: it should be possible to build with JDK17 (being Temurin or others) with target level 11 but it will create all sorts of problems, so better to stick to a JDK11.