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.

Sign up for GitHub

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

Jump to bottom

Update 0004-cocoapods-support-improvements.md #439

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update 0004-cocoapods-support-improvements.md #439

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions proposals/0004-cocoapods-support-improvements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,6 +98,7 @@ Why should we _not_ do this? Please consider:
## Alternatives

- CocoaPods support could be handled by [shipping binaries](https://github.com/react-native-community/discussions-and-proposals/issues/15) of React Native to clients. Personally, I prefer to be working with the source code for ease of forkability and debugging.
- CocoaPods adds unnecessary overhead adoption friction for new developers wanting to simply try out React Native. Swift Package Manager bypasses this friction. Suggest making React Native available as a Swift Package.

## Adoption strategy

Expand Down