This issues tracks various tasks for removing forked, third-party dependencies for the native mobile editor. The following tasks could likely be addressed individually as miniature projects.
We could remove dependency on the forked dependencies by committing fixes/required changes to the upstream repositories or internalizing the dependency in the form of implementing the dependency in the Gutenberg code directly.
This issues tracks various tasks for removing forked, third-party dependencies for the native mobile editor. The following tasks could likely be addressed individually as miniature projects.
What problem does this address?
The forked dependencies have caused issues in the past, e.g. https://github.com/WordPress/gutenberg/issues/33424, https://github.com/WordPress/gutenberg/issues/40540. We have adapted our approach to work around these issues, but the forked dependencies remain an inefficiency.
Current State
What is your proposed solution?
We could remove dependency on the forked dependencies by committing fixes/required changes to the upstream repositories or internalizing the dependency in the form of implementing the dependency in the Gutenberg code directly.
react-native-reanimated
forked repository.react-native-prompt-android
forked repository.react-native-video
forked repository.@react-native-community/slider@4.x
and replace forked repository.[^1]: The modification is made to Podfile to fix an actual issue from the upstream repository.