| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| posthog-react-native@4.65.0 source code.tar.gz | < 14 hours ago | 31.5 MB | |
| posthog-react-native@4.65.0 source code.zip | < 14 hours ago | 33.3 MB | |
| README.md | < 14 hours ago | 2.6 kB | |
| Totals: 3 Items | 64.8 MB | 0 | |
4.65.0
Minor Changes
- #4643
35dcb94Thanks @ioannisj! - Autocapture touches and clicks on React Native Web (including expo-router on web). Touch events there carry no_targetInstand every touch was silently dropped, so the element chain is now resolved by walking up frome.targetto the nearest node carrying a React fiber.captureTouchesalso registers a capture-phaseclicklistener on the document on web, emitted with$event_type: 'click', since browsers firetouchendonly for touch input (react-native-web'sPressablestops propagation, andModalrenders outside the provider's subtree). Autocapture no longer lets an exception escape into the host app's event dispatch. (2026-08-26)
Patch Changes
-
#4650
e03f5d1Thanks @marandaneto! - Accept CSS-style survey positions such asbottom-rightand align them with their canonicalSurveyPositionvalues. (2026-08-26) -
#4654
aad1494Thanks @marandaneto! - Deduplicate unknown survey position warnings after normalizing equivalent position names. (2026-08-26) -
#4649
ec78decThanks @github-actions! - Respectph-no-captureon any ancestor of a touched or clicked element. Previously an interaction deep inside an opted-out subtree could still send an$autocaptureevent carrying that subtree's element text and props, so apps relying on a high-levelph-no-capturemay see fewer$autocaptureevents after upgrading. Interactions more than 1000 elements deep in the view hierarchy now produce no$autocaptureevent rather than a truncated one. A non-numericmaxElementsCapturednow falls back to the default of 20 instead of being treated as no cap at all. (2026-08-26) - Updated dependencies [
ab1383a,0d2cf49]: - @posthog/types@1.406.2