Nicolas Charpentier
This is not exactly true, react-native-url-polyfill wraps whatwg-url-without-polyfill, which I also authored. Expo uses the later directly (react-native-url-polyfill’s internals). You won’t be able to install latest whatwg-url releases directly with React Native. Happy to help.
1 1
Samuel
oh fuckin weird - when I remove the polyfill, the Expo implementation still gets overwritten by the shitty RN one
1 1
cinnamon 🐇 🏳️‍⚧️
when i was at hailey's n she was working on the oauth lib we found weird interactions between all the polyfills bsky.app/profile/cinn...
cinnamon 🐇 🏳️‍⚧️@plushie.holdings· 17 Jul 2025
its weird because when u use react-native-url-polyfill it will be there with the broken expo polyfill for a few ticks of the js engine (because modules evaluate in a weird order????) and then it will disappear because url-polyfill doesnt provide a canParse implementation lol
1 1
cinnamon 🐇 🏳️‍⚧️
basically react-native-url-polyfill will override the expo one but then its like worse at it because it also just pulls in whatwg-url but doesnt give u a canParse or some other now-baseline features
1
phil 🫠
i don't think you'd need it anymore, we ship something similar by default. we still have to look into precompiling that into splitting this into a separate hermes bytecode bundle I think, but yea, it's included
1 1
Samuel
yeah I just had a look and it seems it’s exactly the same implementation under the hood
1 1
Onno Benschop
Sorry, no answers, but as a fellow software developer, it's heartening to see that the struggle for documentation is universal .. wait until you try to find the answer for a problem and after laborious search discover your own post. ProTip: Reply to your own post with the answer. Ask me how I know.
1