Add react-native-leap to Community Projects - #112
Open
hung-yueh wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds react-native-leap to the Community Projects → Deployment table: React Native & Expo bindings for the LEAP SDK (current 0.10.x KMP generation) via Nitro Modules.
On npm as
react-native-leap, MIT-licensed. Feature coverage, all validated end-to-end on a physical iPhone and the Android emulator:@react-native-leap/ai, so LEAP models work withstreamText/generateObjectfrom theaipackageLEAP binaries are not re-hosted: iOS fetches Liquid's official XCFramework release at install time (SHA-256-verified), Android pulls
ai.liquid.leap:*from Maven Central.Placed next to the existing React Native entry (expo-leap-sdk, which targets the legacy 0.9 iOS/Android SDKs); this one wraps the unified 0.10.x SDK.