✨ update react-native-buffer and react-native-quick-base64 #1039

Activity

1. wh201906 commented on May 10, 2026

   

   wh201906

   on May 10, 2026

   Contributor

   More actions

   I found some issues in react-native-quick-base64 3.0.0

   1. The behavior of (base64_)decode() changes. According to perf: replace base64.h with simdutf SIMD-accelerated codec craftzdog/react-native-quick-base64#50 and perf(codec): replace base64 codec with simdutf SIMD-accelerated implementation craftzdog/react-native-quick-base64#54, it doesn't accept mid-string padding like SQ==QU0= and throws errors, but Buffer.from(..., 'base64') in Node.js still tries to decode the prefix.
   2. It implicitly increases the RN version requirement. According to craftzdog/react-native-quick-base64@19484ce, it always uses getStringData(), so the minimum RN version requirement is 0.78.0 (ref: react/react-native@c6f1225#diff-549647bf5f56fd88125093915bb651215f42879df46107df4d5d882fd34a4419R414-R417)

   Considering that the fast base64 encoding/decoding path backed by simdutf has been implemented in #976, I think we don't need to upgrade react-native-buffer to 6.1.2 or react-native-quick-base64 to 3.0.0 (It's still possible to update them to newer versions once the issues above are resolved/confirmed to be expected behavior)
2. boorad commented on May 12, 2026

   

   boorad

   on May 12, 2026

   Collaborator

   More actions

   reopen if there are newer versions we want to incorporate
3. boorad

   closed this as completedon May 12, 2026
4. xgiovio commented on May 12, 2026

   

   xgiovio

   on May 12, 2026

   Author

   More actions

   thanks