chore: deprecate v8 / non-modular methods prior to next major release #8261
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.
Description
These have all been well-reviewed and are the core of a couple follow-on PRs even
main keeps moving along though and this branch attracts entropic failures, so in discussion with Russell we're going to land these three commits then rebase the further v8-deprecation work off main
Related issues
No related issues, but the v8 APIs need to be removed and we have to follow a deprecation cycle to do so
Release Summary
3 conventional commits, semantic release will handle them nicely
Checklist
AndroidiOSe2etests added or updated inpackages/\*\*/e2ejesttests added or updated inpackages/\*\*/__tests__Test Plan
So much testing - all Russell's work on the jest area 💪
Think
react-native-firebaseis great? Please consider supporting the project with any of the below:React Native FirebaseandInvertaseon Twitter