[ Proof ]
react-native-nitro-buffer
unchanged package JavaScript runs over the installed provider, whose C++ (HybridNitroBuffer and simdutf) is compiled to wasm by the Nitro source path; no seam or hand port answers NitroBuffer. A Linux open without a Mac workspace compiles and registers it.100%
API coverageWorking
a 0.4.1 app runs 119 Buffer cases and 87 match Node: utf8, hex, base64, base64url, latin1, utf16le, Unicode and invalid-byte decoding, a 1 MiB base64 and hex round trip, fill, copy, compare, indexOf, typed reads and writes, unknown-encoding errors, and slices share memory
Missing
out-of-range write, fill, copy and compare arguments clamp instead of throwing, errors other than unknown encoding carry no Node code, a UTF-8 write can end inside a character, negative indexOf offsets differ, and the provider is not compared with a native oracle