Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update react-native version #340

Closed
wants to merge 13 commits into from

Conversation

wojteg1337
Copy link

I've upgraded react-native to 60.0 in library and example project, next step will be to create bindings and specs for turbo module support.

Copy link
Contributor

@osdnk osdnk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lovely! I'm not super super about the implication of moving to AndroidX. Could you tell me more about it? Are we going to drop support for prev version then?

@@ -27,6 +27,7 @@ repositories {
// https://github.com/facebook/react-native/blob/1e8f3b11027fe0a7514b4fc97d0798d3c64bc895/local-cli/templates/HelloWorld/android/build.gradle#L21
url "$projectDir/../node_modules/react-native/android"
}
google()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it needed?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nope, removed google repo

@@ -16,5 +16,3 @@ org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryErro
# This option should only be used with decoupled projects. More details, visit
# http://www.gradle.org/docs/current/userguide/multi_project_builds.html#sec:decoupled_projects
# org.gradle.parallel=true

android.useDeprecatedNdk=true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hm?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

while building example project i noticed:

image

so decided to remove it

import android.view.ViewGroup;

import androidx.annotation.Nullable;
import androidx.transition.ChangeBounds;
import androidx.transition.ChangeTransform;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we will be still able to use in old RN version

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this will be compatible with the old RN version. However, we can manually write a doc for those who use react-native version below 0.60.

@@ -0,0 +1,3 @@
module.exports = {
presets: ['module:metro-react-native-babel-preset'],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't we drop .babelrc then?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, I have removed .babelrc file

@@ -0,0 +1,49 @@
platform :ios, '9.0'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great!

@wojteg1337
Copy link
Author

wojteg1337 commented Jul 11, 2019

Lovely! I'm not super super about the implication of moving to AndroidX. Could you tell me more about it? Are we going to drop support for prev version then?

Probably yes, this is breaking change, users with older versions of RN will have to use current stable version or update their projects.

There is an option to reverse Jetifier with react-native-bob, so we could support older versions of react-native.

@rozPierog
Copy link

What is the status of this PR @osdnk? I would love to go back to using "official" version without relying on fork

@osdnk
Copy link
Contributor

osdnk commented Jul 23, 2019

Can’t we use jettifier?

@rozPierog
Copy link

rozPierog commented Jul 23, 2019

Jetifier is quick and dirty fix for library maitainers that aren't willing to spend much time trying to get AndroidX to work properly. The truth is, AndroidX is replacing Android Support library, and not supporting it (pun not inteded) fully you are just asking for trouble when api changes. Everyone back on RN <0.60 will still be able to use older versions of this package without problems. Updating RN to current version is now easier than ever with tools like upgrade-helper
BTW Jetifier has reverse option that is able to change AndoridX back to Support Library so if someone is using 0.59 and really needs new version of some library they can use that to make it work.

@dulmandakh dulmandakh mentioned this pull request Sep 20, 2019
@kmagiera
Copy link
Member

Thanks for submitting this PR, as I've just merged #395 which covers the migration I'm going to close this one. Thank you for your contribution regardless 🙌

@kmagiera kmagiera closed this Sep 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants