Migrate React Native CLI (RN v0.60.x)

[nineto4]

Migrate React Native CLI
https://github.com/react-native-community/cli/blob/master/docs/configuration.md#migration-guide

[msftclas]

All CLA requirements met.

[congnguyen91]

+1 this should be checked :)

[v0lume]

can it be merged asap cause i don't want to see this errors anymore?

[aarongrider]

Bump on this!

[namvoeh]

@nineto4 it's missing postlink and postunlink hooks, please check my PR #1699

[birkir]

Cool, react-native-code-push is currently blocking RN 0.60 and 0.61 users from using the auto-linking feature.

@alexandergoncharov can you merge and release a new version?

[namvoeh]

Please help to merge this 2 months old PR

[nineto4]

Updated: alphabetical order

[builtbyproxy]

Feel free to dismiss.
However, a lot of people are currently going through their node_modules to tweak specific things to their project. Could we use this chance to document what we are actually doing?

Including this link would be great: https://stackoverflow.com/questions/18641994/how-getresources-getstring-works-android

Also, if it was commands should it not still be commands? I thought only hooks translated to hooks

Thanks!

[giacomocerquone]

@builtbyproxy actually I believe that the use of prelink and postunlink "reserved" words in the commands object relies on a quite old rnpm version (in fact you can still find it in their locked repo https://github.com/rnpm/rnpm).
So it should be something that was already moved to the hooks object.

But I want to make clear that these are all assumptions and I couldn't find absolutely anything about how rnpm should be configured for a native lib. The only thing that drives me to that conclusion is the rnpm doc (showing an old commands-prelink/postlink configuration) and the migration guide (showing a prelink field inside the hooks object https://github.com/react-native-community/cli/blob/master/docs/configuration.md#libraries)

[builtbyproxy]

@giacomocerquone Absolutely Fantastic! Thanks a lot for explaining all of that!
Do you know what's blocking this merge?

[giacomocerquone]

@builtbyproxy the stale situation of this repo is blocking the merge.
I read comments of almost a year ago that the project went under a heavy modification process by the core team and I kept reading of people who's claiming that the project is not dead... yeah, probably, but surely I don't think this is the proper way to handle a migration. No public WIP board, no way we can help since the work is not being done through this repo... this doesn't look like OSS honestly 😅

To make people happy, it was as simple as declaring 1 or 2 trustable people that would have taken care of updating the docs, merging pull request of few lines like this etc. Etc.

Don't want to disrespect with this comment... we all rely on this package, and the devs did and I'm sure are still doing a great work, but just wanted to note this in order to handle the next "project rework" there might be a little bit better.

Honestly I'd like to help managing the issues and the pull requests, but no one would give me credit nor permission 😊

[bitlab-code]

Absolutely agree with what @giacomocerquone says
Without wishing to be pessimistic, everything suggests that Microsoft no longer has an interest in CodePush and React Native. Too much silence is probably "The beginning of the end", perhaps this "next version of CodePush" will be a new appcenter service

[giacomocerquone]

Well @bitlab-code I wouldn't say that. React Native seems to be very important to Microsoft*, I just said that things could have done in a cleaner and more proper way, and actually like this is some sort of a disaster.

*https://www.theregister.co.uk/2019/11/07/microsoft_react_native/
*https://twitter.com/reactiflux/status/1184927584502665217

[builtbyproxy]

@giacomocerquone Who do we need to bug to get this stuff approved?
My patch-package for this is starting to get a bit overwhelming

[giacomocerquone]

Let's just ping the main contributors: @geof90 @lostintangent @max-mironov @alexandergoncharov the community needs you, I hope you won't be bothered by this request!
Thank you very much for consideration.

[joseph-d-p]

See PR #1735

[builtbyproxy]

Opened by a member of Microsoft :O

[alexandergoncharov-zz]

Hi all,
Thanks for contributing and sorry for this big delay!

I think that it was fixed a long time ago by #1735.
So, I'm going to close this PR for now. Please feel free to reopen it if you have any questions!