Overly high JS baseline requirement, from using URL.canParse()

[Tristan971]

Hello,

In here, the library has begun using URL.canParse():

https://github.com/braintree/sanitize-url/blame/cdd33eb72e9f56eff7b3c49f1c5ed133838b9956/src/index.ts#L24

This imposes a surprisingly strict requirement on browser versions (https://caniuse.com/?search=canParse):

• Safari/iOS 17.0
• Firefox 125
• Chromium 120

As far as I can tell, it has as a result only been widely available since ~ December 2023.

I don't mind it necessarily, but it is a huge enough jump that I'd suggest making it in a major version update.

I'm not sure what the previous minimal browser version set was exactly, but at least up to iOS 14 worked, going by the browsers we had successfully tested on our own website.

[akphi]

though rather unrelated, I would like to mention that this makes testing with Jest a little less convenient since URL.canParse is not implemented in jsdom

[erquhart]

This also breaks compatibility with React Native. I realize this was to address a security issue, but it's also a breaking change in a minor release, and should be reverted for that reason alone.

Related PR: #77

cc/ @ibooker

[ibooker]

Hello,
@Tristan971 Thanks for reporting this issue with URL.canParse(). We'll take a closer look at this issue. (Internal Tracking: BTWEB-171)

@erquhart We do not specifically support compatibility with React Native. If you can provides some details about what no longer works, we can better understand if its something we can address.

[erquhart]

@ibooker I don't see anything in the repo stating explicit support for any platform, browser etc., I'm just adding React Native to the list of environments for which this library no longer works.

I don't have a separate issue to outline, just that the use of URL.canParse() is not supported in React Native, as well as a fair amount of browser versions and jsdom, as mentioned by others.

[chrisvanpatten]

Agree, 7.1.0 should have been released as 8.0.0; effectively dropping support for older Nodes, whether intentional or not, is a breaking change.

[patocallaghan]

@ibooker just wondering if there will be a newer version of 7.x which will ship without theURL.canParse change? I see some new releases have shipped but we can't upgrade due to our browser support. We could use patch package but would rather only do that as a last resort.

[samuel871211]

Workaround:

core-js provides a polyfill for URL.canParse
https://github.com/zloirock/core-js/blob/master/packages/core-js/modules/web.url.can-parse.js
I'm currently configuring in my webpack.