Undo a rearchitecture that breaks us downstream by HeyImChris · Pull Request #777 · microsoft/react-native-macos

HeyImChris · 2021-05-20T21:14:33Z

Please select one of the following

I am removing an existing difference between facebook/react-native and microsoft/react-native-macos 👍
I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos 👍
I am making a fix / change for the macOS implementation of react-native
I am making a change required for Microsoft usage of react-native

Summary

This change I'm reverting for the 63 stable branch is an improvement in that we only do the global JS variable init once, but it has the downside that it splits out the JS runtime init from the bundle loading which breaks a scenario we rely on downstream.

I'm still investigating how to rearchitect our downstream client code to be compatible with this change which is why I'm just making this revert in 0.63 instead of master. In the short term, we need to unblock ourselves and anyone else that isn't set up to properly handle this new scenario of rearchitecting the SDX setup.

I also hit some failures using Flipper. We need a different version than is compatible so for now I disabled Flipper as we don't need it on.

git revert 6f627f684bb6506a677c9632b2710e4a541690a9

Changelog

[General] [Minor] - git revert a 63 initialization rearchitecture

Test Plan

This is going back to what is in 0.62 so it should all still work as well as 0.62 did. I ran the test app and basic scenarios seem to still work as expected.

* Update RCTCxxBridge.mm * add nullability checks

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

Pull Request Analyser (pull-bot) · 2021-05-20T21:17:05Z

	Warnings
⚠️	❔ Base Branch - The base branch for this PR is something other than `master`. Are you sure you want to merge these changes into a stable release? If you are interested in backporting updates to an older release, the suggested approach is to land those changes on `master` first and then cherry-pick the commits into the branch for that release. The Releases Guide has more information.

	Messages
📖	📋 Verify Changelog Format - A changelog entry has the following format: `[CATEGORY] [TYPE] - Message`. Details CATEGORY may be: General macOS iOS Android JavaScript Internal (for changes that do not need to be called out in the release notes) TYPE may be: Added, for new features. Changed, for changes in existing functionality. Deprecated, for soon-to-be removed features. Removed, for now removed features. Fixed, for any bug fixes. Security, in case of vulnerabilities. MESSAGE may answer "what and why" on a feature level. Use this to briefly tell React Native users about notable changes.

Generated by 🚫 dangerJS against 5d320f4

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

This reverts commit 73224cf.

This reverts commit 73224cf, which itself was a revert of a commit. So we're bringing back the original change. We thought it would break things downstream for us, but are electing to instead fix things downstream rather than undo this commit.

HeyImChris · 2021-05-20T21:14:33Z

Please select one of the following

I am removing an existing difference between facebook/react-native and microsoft/react-native-macos 👍
I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos 👍
I am making a fix / change for the macOS implementation of react-native
I am making a change required for Microsoft usage of react-native

Summary

This change I'm reverting for the 63 stable branch is an improvement in that we only do the global JS variable init once, but it has the downside that it splits out the JS runtime init from the bundle loading which breaks a scenario we rely on downstream.

I'm still investigating how to rearchitect our downstream client code to be compatible with this change which is why I'm just making this revert in 0.63 instead of master. In the short term, we need to unblock ourselves and anyone else that isn't set up to properly handle this new scenario of rearchitecting the SDX setup.

I also hit some failures using Flipper. We need a different version than is compatible so for now I disabled Flipper as we don't need it on.

git revert 6f627f684bb6506a677c9632b2710e4a541690a9

Changelog

[General] [Minor] - git revert a 63 initialization rearchitecture

Test Plan

This is going back to what is in 0.62 so it should all still work as well as 0.62 did. I ran the test app and basic scenarios seem to still work as expected.

* Update RCTCxxBridge.mm * add nullability checks

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

Pull Request Analyser (pull-bot) · 2021-05-20T21:17:05Z

	Warnings
⚠️	❔ Base Branch - The base branch for this PR is something other than `master`. Are you sure you want to merge these changes into a stable release? If you are interested in backporting updates to an older release, the suggested approach is to land those changes on `master` first and then cherry-pick the commits into the branch for that release. The Releases Guide has more information.

	Messages
📖	📋 Verify Changelog Format - A changelog entry has the following format: `[CATEGORY] [TYPE] - Message`. Details CATEGORY may be: General macOS iOS Android JavaScript Internal (for changes that do not need to be called out in the release notes) TYPE may be: Added, for new features. Changed, for changes in existing functionality. Deprecated, for soon-to-be removed features. Removed, for now removed features. Fixed, for any bug fixes. Security, in case of vulnerabilities. MESSAGE may answer "what and why" on a feature level. Use this to briefly tell React Native users about notable changes.

Generated by 🚫 dangerJS against 5d320f4

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

This reverts commit 73224cf.

This reverts commit 73224cf, which itself was a revert of a commit. So we're bringing back the original change. We thought it would break things downstream for us, but are electing to instead fix things downstream rather than undo this commit.

HeyImChris · 2021-05-20T21:14:33Z

Please select one of the following

I am removing an existing difference between facebook/react-native and microsoft/react-native-macos 👍
I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos 👍
I am making a fix / change for the macOS implementation of react-native
I am making a change required for Microsoft usage of react-native

Summary

This change I'm reverting for the 63 stable branch is an improvement in that we only do the global JS variable init once, but it has the downside that it splits out the JS runtime init from the bundle loading which breaks a scenario we rely on downstream.

I'm still investigating how to rearchitect our downstream client code to be compatible with this change which is why I'm just making this revert in 0.63 instead of master. In the short term, we need to unblock ourselves and anyone else that isn't set up to properly handle this new scenario of rearchitecting the SDX setup.

I also hit some failures using Flipper. We need a different version than is compatible so for now I disabled Flipper as we don't need it on.

git revert 6f627f684bb6506a677c9632b2710e4a541690a9

Changelog

[General] [Minor] - git revert a 63 initialization rearchitecture

Test Plan

This is going back to what is in 0.62 so it should all still work as well as 0.62 did. I ran the test app and basic scenarios seem to still work as expected.

* Update RCTCxxBridge.mm * add nullability checks

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

Pull Request Analyser (pull-bot) · 2021-05-20T21:17:05Z

	Warnings
⚠️	❔ Base Branch - The base branch for this PR is something other than `master`. Are you sure you want to merge these changes into a stable release? If you are interested in backporting updates to an older release, the suggested approach is to land those changes on `master` first and then cherry-pick the commits into the branch for that release. The Releases Guide has more information.

	Messages
📖	📋 Verify Changelog Format - A changelog entry has the following format: `[CATEGORY] [TYPE] - Message`. Details CATEGORY may be: General macOS iOS Android JavaScript Internal (for changes that do not need to be called out in the release notes) TYPE may be: Added, for new features. Changed, for changes in existing functionality. Deprecated, for soon-to-be removed features. Removed, for now removed features. Fixed, for any bug fixes. Security, in case of vulnerabilities. MESSAGE may answer "what and why" on a feature level. Use this to briefly tell React Native users about notable changes.

Generated by 🚫 dangerJS against 5d320f4

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

This reverts commit 73224cf.

This reverts commit 73224cf, which itself was a revert of a commit. So we're bringing back the original change. We thought it would break things downstream for us, but are electing to instead fix things downstream rather than undo this commit.

HeyImChris · 2021-05-20T21:14:33Z

Please select one of the following

I am removing an existing difference between facebook/react-native and microsoft/react-native-macos 👍
I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos 👍
I am making a fix / change for the macOS implementation of react-native
I am making a change required for Microsoft usage of react-native

Summary

This change I'm reverting for the 63 stable branch is an improvement in that we only do the global JS variable init once, but it has the downside that it splits out the JS runtime init from the bundle loading which breaks a scenario we rely on downstream.

I'm still investigating how to rearchitect our downstream client code to be compatible with this change which is why I'm just making this revert in 0.63 instead of master. In the short term, we need to unblock ourselves and anyone else that isn't set up to properly handle this new scenario of rearchitecting the SDX setup.

I also hit some failures using Flipper. We need a different version than is compatible so for now I disabled Flipper as we don't need it on.

git revert 6f627f684bb6506a677c9632b2710e4a541690a9

Changelog

[General] [Minor] - git revert a 63 initialization rearchitecture

Test Plan

This is going back to what is in 0.62 so it should all still work as well as 0.62 did. I ran the test app and basic scenarios seem to still work as expected.

* Update RCTCxxBridge.mm * add nullability checks

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

Pull Request Analyser (pull-bot) · 2021-05-20T21:17:05Z

	Warnings
⚠️	❔ Base Branch - The base branch for this PR is something other than `master`. Are you sure you want to merge these changes into a stable release? If you are interested in backporting updates to an older release, the suggested approach is to land those changes on `master` first and then cherry-pick the commits into the branch for that release. The Releases Guide has more information.

	Messages
📖	📋 Verify Changelog Format - A changelog entry has the following format: `[CATEGORY] [TYPE] - Message`. Details CATEGORY may be: General macOS iOS Android JavaScript Internal (for changes that do not need to be called out in the release notes) TYPE may be: Added, for new features. Changed, for changes in existing functionality. Deprecated, for soon-to-be removed features. Removed, for now removed features. Fixed, for any bug fixes. Security, in case of vulnerabilities. MESSAGE may answer "what and why" on a feature level. Use this to briefly tell React Native users about notable changes.

Generated by 🚫 dangerJS against 5d320f4

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

This reverts commit 73224cf.

This reverts commit 73224cf, which itself was a revert of a commit. So we're bringing back the original change. We thought it would break things downstream for us, but are electing to instead fix things downstream rather than undo this commit.

HeyImChris · 2021-05-20T21:14:33Z

Please select one of the following

I am removing an existing difference between facebook/react-native and microsoft/react-native-macos 👍
I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos 👍
I am making a fix / change for the macOS implementation of react-native
I am making a change required for Microsoft usage of react-native

Summary

This change I'm reverting for the 63 stable branch is an improvement in that we only do the global JS variable init once, but it has the downside that it splits out the JS runtime init from the bundle loading which breaks a scenario we rely on downstream.

I'm still investigating how to rearchitect our downstream client code to be compatible with this change which is why I'm just making this revert in 0.63 instead of master. In the short term, we need to unblock ourselves and anyone else that isn't set up to properly handle this new scenario of rearchitecting the SDX setup.

I also hit some failures using Flipper. We need a different version than is compatible so for now I disabled Flipper as we don't need it on.

git revert 6f627f684bb6506a677c9632b2710e4a541690a9

Changelog

[General] [Minor] - git revert a 63 initialization rearchitecture

Test Plan

This is going back to what is in 0.62 so it should all still work as well as 0.62 did. I ran the test app and basic scenarios seem to still work as expected.

* Update RCTCxxBridge.mm * add nullability checks

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

Pull Request Analyser (pull-bot) · 2021-05-20T21:17:05Z

	Warnings
⚠️	❔ Base Branch - The base branch for this PR is something other than `master`. Are you sure you want to merge these changes into a stable release? If you are interested in backporting updates to an older release, the suggested approach is to land those changes on `master` first and then cherry-pick the commits into the branch for that release. The Releases Guide has more information.

	Messages
📖	📋 Verify Changelog Format - A changelog entry has the following format: `[CATEGORY] [TYPE] - Message`. Details CATEGORY may be: General macOS iOS Android JavaScript Internal (for changes that do not need to be called out in the release notes) TYPE may be: Added, for new features. Changed, for changes in existing functionality. Deprecated, for soon-to-be removed features. Removed, for now removed features. Fixed, for any bug fixes. Security, in case of vulnerabilities. MESSAGE may answer "what and why" on a feature level. Use this to briefly tell React Native users about notable changes.

Generated by 🚫 dangerJS against 5d320f4

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

This reverts commit 73224cf.

This reverts commit 73224cf, which itself was a revert of a commit. So we're bringing back the original change. We thought it would break things downstream for us, but are electing to instead fix things downstream rather than undo this commit.

HeyImChris · 2021-05-20T21:14:33Z

Please select one of the following

I am removing an existing difference between facebook/react-native and microsoft/react-native-macos 👍
I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos 👍
I am making a fix / change for the macOS implementation of react-native
I am making a change required for Microsoft usage of react-native

Summary

This change I'm reverting for the 63 stable branch is an improvement in that we only do the global JS variable init once, but it has the downside that it splits out the JS runtime init from the bundle loading which breaks a scenario we rely on downstream.

I'm still investigating how to rearchitect our downstream client code to be compatible with this change which is why I'm just making this revert in 0.63 instead of master. In the short term, we need to unblock ourselves and anyone else that isn't set up to properly handle this new scenario of rearchitecting the SDX setup.

I also hit some failures using Flipper. We need a different version than is compatible so for now I disabled Flipper as we don't need it on.

git revert 6f627f684bb6506a677c9632b2710e4a541690a9

Changelog

[General] [Minor] - git revert a 63 initialization rearchitecture

Test Plan

This is going back to what is in 0.62 so it should all still work as well as 0.62 did. I ran the test app and basic scenarios seem to still work as expected.

* Update RCTCxxBridge.mm * add nullability checks

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

Pull Request Analyser (pull-bot) · 2021-05-20T21:17:05Z

	Warnings
⚠️	❔ Base Branch - The base branch for this PR is something other than `master`. Are you sure you want to merge these changes into a stable release? If you are interested in backporting updates to an older release, the suggested approach is to land those changes on `master` first and then cherry-pick the commits into the branch for that release. The Releases Guide has more information.

	Messages
📖	📋 Verify Changelog Format - A changelog entry has the following format: `[CATEGORY] [TYPE] - Message`. Details CATEGORY may be: General macOS iOS Android JavaScript Internal (for changes that do not need to be called out in the release notes) TYPE may be: Added, for new features. Changed, for changes in existing functionality. Deprecated, for soon-to-be removed features. Removed, for now removed features. Fixed, for any bug fixes. Security, in case of vulnerabilities. MESSAGE may answer "what and why" on a feature level. Use this to briefly tell React Native users about notable changes.

Generated by 🚫 dangerJS against 5d320f4

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

This reverts commit 73224cf.

This reverts commit 73224cf, which itself was a revert of a commit. So we're bringing back the original change. We thought it would break things downstream for us, but are electing to instead fix things downstream rather than undo this commit.

HeyImChris · 2021-05-20T21:14:33Z

Please select one of the following

I am removing an existing difference between facebook/react-native and microsoft/react-native-macos 👍
I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos 👍
I am making a fix / change for the macOS implementation of react-native
I am making a change required for Microsoft usage of react-native

Summary

This change I'm reverting for the 63 stable branch is an improvement in that we only do the global JS variable init once, but it has the downside that it splits out the JS runtime init from the bundle loading which breaks a scenario we rely on downstream.

I'm still investigating how to rearchitect our downstream client code to be compatible with this change which is why I'm just making this revert in 0.63 instead of master. In the short term, we need to unblock ourselves and anyone else that isn't set up to properly handle this new scenario of rearchitecting the SDX setup.

I also hit some failures using Flipper. We need a different version than is compatible so for now I disabled Flipper as we don't need it on.

git revert 6f627f684bb6506a677c9632b2710e4a541690a9

Changelog

[General] [Minor] - git revert a 63 initialization rearchitecture

Test Plan

This is going back to what is in 0.62 so it should all still work as well as 0.62 did. I ran the test app and basic scenarios seem to still work as expected.

* Update RCTCxxBridge.mm * add nullability checks

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

Pull Request Analyser (pull-bot) · 2021-05-20T21:17:05Z

	Warnings
⚠️	❔ Base Branch - The base branch for this PR is something other than `master`. Are you sure you want to merge these changes into a stable release? If you are interested in backporting updates to an older release, the suggested approach is to land those changes on `master` first and then cherry-pick the commits into the branch for that release. The Releases Guide has more information.

	Messages
📖	📋 Verify Changelog Format - A changelog entry has the following format: `[CATEGORY] [TYPE] - Message`. Details CATEGORY may be: General macOS iOS Android JavaScript Internal (for changes that do not need to be called out in the release notes) TYPE may be: Added, for new features. Changed, for changes in existing functionality. Deprecated, for soon-to-be removed features. Removed, for now removed features. Fixed, for any bug fixes. Security, in case of vulnerabilities. MESSAGE may answer "what and why" on a feature level. Use this to briefly tell React Native users about notable changes.

Generated by 🚫 dangerJS against 5d320f4

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

This reverts commit 73224cf.

This reverts commit 73224cf, which itself was a revert of a commit. So we're bringing back the original change. We thought it would break things downstream for us, but are electing to instead fix things downstream rather than undo this commit.

HeyImChris · 2021-05-20T21:14:33Z

Please select one of the following

I am removing an existing difference between facebook/react-native and microsoft/react-native-macos 👍
I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos 👍
I am making a fix / change for the macOS implementation of react-native
I am making a change required for Microsoft usage of react-native

Summary

This change I'm reverting for the 63 stable branch is an improvement in that we only do the global JS variable init once, but it has the downside that it splits out the JS runtime init from the bundle loading which breaks a scenario we rely on downstream.

I'm still investigating how to rearchitect our downstream client code to be compatible with this change which is why I'm just making this revert in 0.63 instead of master. In the short term, we need to unblock ourselves and anyone else that isn't set up to properly handle this new scenario of rearchitecting the SDX setup.

I also hit some failures using Flipper. We need a different version than is compatible so for now I disabled Flipper as we don't need it on.

git revert 6f627f684bb6506a677c9632b2710e4a541690a9

Changelog

[General] [Minor] - git revert a 63 initialization rearchitecture

Test Plan

This is going back to what is in 0.62 so it should all still work as well as 0.62 did. I ran the test app and basic scenarios seem to still work as expected.

* Update RCTCxxBridge.mm * add nullability checks

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

Pull Request Analyser (pull-bot) · 2021-05-20T21:17:05Z

	Warnings
⚠️	❔ Base Branch - The base branch for this PR is something other than `master`. Are you sure you want to merge these changes into a stable release? If you are interested in backporting updates to an older release, the suggested approach is to land those changes on `master` first and then cherry-pick the commits into the branch for that release. The Releases Guide has more information.

	Messages
📖	📋 Verify Changelog Format - A changelog entry has the following format: `[CATEGORY] [TYPE] - Message`. Details CATEGORY may be: General macOS iOS Android JavaScript Internal (for changes that do not need to be called out in the release notes) TYPE may be: Added, for new features. Changed, for changes in existing functionality. Deprecated, for soon-to-be removed features. Removed, for now removed features. Fixed, for any bug fixes. Security, in case of vulnerabilities. MESSAGE may answer "what and why" on a feature level. Use this to briefly tell React Native users about notable changes.

Generated by 🚫 dangerJS against 5d320f4

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

…ve-macos into 0.63-stable

…ndle (react#27844)" This reverts commit 6f627f6.

…ative-macos into 63_initRearch

This reverts commit 73224cf.

This reverts commit 73224cf, which itself was a revert of a commit. So we're bringing back the original change. We thought it would break things downstream for us, but are electing to instead fix things downstream rather than undo this commit.

HeyImChrisand others added 16 commits February 4, 2021 11:38

Add nullability checks (microsoft#704)
6f008d6
* Update RCTCxxBridge.mm * add nullability checks

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
a973d02
…ve-macos into 0.63-stable

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
a265b19
…ve-macos into 0.63-stable

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
02f7a84
…ve-macos into 0.63-stable

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
fcc450d
…ve-macos into 0.63-stable

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
4f93eef
…ve-macos into 0.63-stable

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
6b1f7df
…ve-macos into 0.63-stable

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
f341932
…ve-macos into 0.63-stable

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
2fb8131
…ve-macos into 0.63-stable

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
7a9a99f
…ve-macos into 0.63-stable

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
2ec3692
…ve-macos into 0.63-stable

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
b20bc04
…ve-macos into 0.63-stable

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
2496154
…ve-macos into 0.63-stable

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
894748c
…ve-macos into 0.63-stable

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
36fcf6b
…ve-macos into 0.63-stable

Revert "Split loadApplicationScript into initializeRuntime and loadBu…
c1c88f0
…ndle (react#27844)" This reverts commit 6f627f6.

HeyImChris requested a review from Harrie Shin (harrieshin)May 20, 2021 21:14

HeyImChris requested a review from Eloy Durán (alloy) as a code owner May 20, 2021 21:14

HeyImChris requested a review from Adam Gleitman (amgleitman)May 20, 2021 21:14

HeyImChris added 10 commits May 21, 2021 10:51

pod fixes
64d6f42

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
ae62c76
…ve-macos into 0.63-stable

Revert "Split loadApplicationScript into initializeRuntime and loadBu…
36501ac
…ndle (react#27844)" This reverts commit 6f627f6.

pod fixes
970856c

pod update
693c686

Merge branch '63_initRearch' ofhttps://github.com/HeyImChris/react-n…
838a741
…ative-macos into 63_initRearch

pod install
810774a

fix libevents and flipper dependencies
eefc9d4

flipper updates
e9e5f71

Merge branch '63_initRearch' ofhttps://github.com/HeyImChris/react-n…
33ca6cf
…ative-macos into 63_initRearch

HeyImChrisand others added 9 commits June 1, 2021 11:46

disable sonar kit
956c612

Merge branch '0.63-stable' ofhttps://github.com/microsoft/react-nati…
3fdb782
…ve-macos into 0.63-stable

Revert "Split loadApplicationScript into initializeRuntime and loadBu…
6efc86a
…ndle (react#27844)" This reverts commit 6f627f6.

pod fixes
4e9ec1a

flipper updates
300c217

disable sonar kit
68f17c6

Merge branch '0.63-stable' into 63_initRearch
d0b70bd

Merge branch '63_initRearch' ofhttps://github.com/HeyImChris/react-n…
dda6b70
…ative-macos into 63_initRearch

pod install
5d320f4

HeyImChris requested a review from Saad Najmi (Saadnajmi)June 1, 2021 21:59

Saad Najmi (Saadnajmi) approved these changes Jun 1, 2021
View reviewed changes

HeyImChris merged commit 73224cf into microsoft:0.63-stableJun 1, 2021

Saad Najmi (Saadnajmi) added a commit to Saadnajmi/react-native-macos that referenced this pull request Jun 11, 2021
Revert "Undo a rearchitecture that breaks us downstream (microsoft#777)"
b69e072
This reverts commit 73224cf.