Different behavior from browser URL

[wachunei]

Hello Nicolas, I'm working with IPFS URLS and I noticed the properties are parsed differently than the URL implementation present on the browsers: https://snack.expo.dev/ar0b1IBPg

Is this a bug? I would like to rely on this library to separate the protocol from the rest of the URL in order to replace it with a gateway, what would you recommend to do?

---

Properties of ipfs://QmXnnyufdzAWL5CqZ2RnSNgPbvCc1ALT73s6epPrRnZ1Xy with URL and the polyfill

[charpeni]

👋

I’m not on my computer right now, but I can provide some additional details in the meantime.

The URL implementation provided by default on React Native is buggy and not spec compliant. See the README for more information.

I have more trust in this library!

If we want to compare with browsers implementations, we can look at: https://jsdom.github.io/whatwg-url/#url=aXBmczovL1FtWG5ueXVmZHpBV0w1Q3FaMlJuU05nUGJ2Q2MxQUxUNzNzNmVwUHJSbloxWHk=&base=YWJvdXQ6Ymxhbms=.

Let me know if you have other questions.

[wachunei]

Thank you very much for your promptly response. Wow, so even Browser implementation is not spec compliant? 🤯 I'll rely on this library then! Closing this.

[charpeni]

Well, yes, browser implementations should be fine, the issue relies within React Native because they chose to create a small homemade implementation of URL. So, when you use global URL in React Native, it’s using RN’s polyfill which is buggy and not spec compliant.

More information here: facebook/react-native#30188.