-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
CocoaPods: Split React-jsc out of React-jsi #35031
Conversation
Summary: The React-jsi Pod was serving two purposes: building JSI, and configuring JavaScriptCore as the JS engine. By splitting the React-jsi Pod into React-jsi and React-jsi, we can start working towards de-coupling the JSI dependency from any particular JS engine. Pods that depended on React-jsi, now depend on React-jsi and React-jsc. One exception to this is React-hermes, which is only installed when Hermes is enabled, and thus does not require JavaScriptCore. Upcoming commits should take care of removing the React-jsc dependency when Hermes is enabled, but it is out of scope for this commit. Changelog: [iOS][Changed] - The JSC Runtime is now provided by the React-jsc Pod instead of React-jsi. Libraries that declared a dependency on React-jsi in order to specifically create a JSC runtime (`makeJSCRuntime()`) will need to add React-jsc to their dependencies. Reviewed By: dmytrorykun Differential Revision: D40442603 fbshipit-source-id: 8a956cfa7e2a8fb6d7c3d6967853cdf747ba9d91
This pull request was exported from Phabricator. Differential Revision: D40442603 |
Base commit: be6f656 |
Base commit: e4b5d3e |
PR build artifact for b1c4fe4 is ready. |
PR build artifact for b1c4fe4 is ready. |
This pull request was successfully merged by @hramos in 6b129d8. When will my fix make it into a release? | Upcoming Releases |
Summary: Pull Request resolved: facebook#35031 The React-jsi Pod was serving two purposes: building JSI, and configuring JavaScriptCore as the JS engine. By splitting the React-jsi Pod into React-jsi and React-jsi, we can start working towards de-coupling the JSI dependency from any particular JS engine. Pods that depended on React-jsi, now depend on React-jsi and React-jsc. One exception to this is React-hermes, which is only installed when Hermes is enabled, and thus does not require JavaScriptCore. Upcoming commits should take care of removing the React-jsc dependency when Hermes is enabled, but it is out of scope for this commit. Changelog: [iOS][Changed] - The JSC Runtime is now provided by the React-jsc Pod instead of React-jsi. Libraries that declared a dependency on React-jsi in order to specifically create a JSC runtime (`makeJSCRuntime()`) will need to add React-jsc to their dependencies. Reviewed By: dmytrorykun Differential Revision: D40442603 fbshipit-source-id: b9b21146b9deb401f80cfef76a87c9867754a953
Summary:
The React-jsi Pod was serving two purposes: building JSI, and configuring JavaScriptCore as the JS engine.
By splitting the React-jsi Pod into React-jsi and React-jsi, we can start working towards de-coupling the JSI dependency from any particular JS engine.
Pods that depended on React-jsi, now depend on React-jsi and React-jsc.
One exception to this is React-hermes, which is only installed when Hermes is enabled, and thus does not require JavaScriptCore.
Upcoming commits should take care of removing the React-jsc dependency when Hermes is enabled, but it is out of scope for this commit.
Changelog:
[iOS][Changed] - The JSC Runtime is now provided by the React-jsc Pod instead of React-jsi. Libraries that declared a dependency on React-jsi in order to specifically create a JSC runtime (
makeJSCRuntime()
) will need to add React-jsc to their dependencies.Reviewed By: dmytrorykun
Differential Revision: D40442603