fix: use URL.canParse
instead of runtime deprecated url.parse
api
#150
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
url.parse
is runtime deprecated. It looks like it's being used here to somewhat check if the string is a valid URL, so I've changed that toURL.canParse
which is the compliant way of checking whether a string is a valid and parsable URL.URL.canParse
was added in node18.17.0
and19.9.0
I've backported this to
normalize-package-data
: npm/normalize-package-data#247References
npm/normalize-package-data#242
pnpm/pnpm#9529
https://developer.mozilla.org/en-US/docs/Web/API/URL/canParse_static
https://nodejs.org/api/url.html#urlcanparseinput-base