react-native-firebase
react-native-firebase copied to clipboard
feat(firebase-ai): create `ai` package, `vertexai` wraps around it
Description
- Moved the bulk of code to new
aipackage. Kept relevant types invertexaipackage and deprecated them. - Updated implementation (where possible) to match
firebase-js-sdk. - Updated mocks to match latest implementation on vertexai-sdk-test-data repo which now segments responses from
vertexaiandgoogleai. - I did attempt to symlink ai into vertexai but nested symlinks within directories were not being packaged in
dist/so opted to makeaipackage a dependency which I think is a better way of doing it. - Created an
aiexample app for illustration and tested latestvertexaiandaiimplementations which surfaced a couple of subtle bugs that have been resolved.
Important
- We need to do the same attribution as we did for
vertexaifor this pull request. - Double check what needs to be in the CHANGELOG for this release.
Related issues
Release Summary
Checklist
- I read the Contributor Guide and followed the process outlined there for submitting PRs.
- [ ] Yes
- My change supports the following platforms;
- [ ]
Android - [ ]
iOS - [ ]
Other(macOS, web)
- [ ]
- My change includes tests;
- [ ]
e2etests added or updated inpackages/\*\*/e2e - [ ]
jesttests added or updated inpackages/\*\*/__tests__
- [ ]
- [ ] I have updated TypeScript types that are affected by my change.
- This is a breaking change;
- [ ] Yes
- [ ] No
Test Plan
Think react-native-firebase is great? Please consider supporting the project with any of the below:
- 👉 Star this repo on GitHub ⭐️
- 👉 Follow
React Native FirebaseandInvertaseon Twitter
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| react-native-firebase | Preview | Comment | Aug 18, 2025 0:22am |
Looking into this one now for review - noticed Other tests were failing because TextEncoder implementation seems to be missing and is needed ? Unexpected as it seems that should have been failing for a while if so, but...okay
rebased to main and put an in situ implementation of the string -> uint8array conversion in the storage library and it passes locally, hopefully this goes green in CI - will finish the review later