Fallback to unstable_getBoundingClientRect if available #420
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.
This was recently changed as part of the refactoring of 74562f4#diff-bcc5857af5fe29c6679b5afaf39db7eed5fc74a15ab118691ee8c13c5954b70eL75
this implicitly binds react-strict-dom to require at least react-native 0.82.
Is that intentional?
Is there a place where the minimum required version is explicitly listed?
In that case, then maybe was just forgotten to update the peer dependency here: https://github.com/facebook/react-strict-dom/blob/main/packages/react-strict-dom/package.json#L62
Feel free to close in case, and treat this PR as a small question with a code snippet