[Snyk] Upgrade whatwg-url from 7.1.0 to 14.0.0 #3
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.
Snyk has created this PR to upgrade whatwg-url from 7.1.0 to 14.0.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 18 versions ahead of your current version.
The recommended version was released on a year ago.
Release notes
Package name: whatwg-url
Breaking change: removed Node.js v16 support.
Breaking change: removed Node.js v14 support.
Added
URL.canParse()
, per whatwg/url@ae3c28b.Added
URLSearchParams
'ssize
getter, per whatwg/url@12b6f0c.Added optional second
value
argument toURLSearchParams
'shas()
anddelete()
methods, per whatwg/url@bfb9157.Changed the serialization of the origin of
blob:
URLs whose inner URLs were nothttp:
orhttps:
to be"null"
, per whatwg/url@eee49fd.Updated our
tr46
dependency, which brings along several fixes related to international domain names. Such as:https://xn--4-0bd15808a.../
, no longer cause URL parsing to fail.http://xn--ls8h=/
, now correctly cause URL parsing to fail.As part of this, we are now running against the newly-introduced test data derived from the Unicode Consortium-maintained
IdnaTestV2.txt
file, and passing them all.Breaking change: removed Node.js v12 support.
Changed the characters allowed in domains vs. generic hosts, per whatwg/url@35e195a.
Changed the
URL
API'ssearch
andhash
setters, as well as theURLSearchParams
API, to always ensure the URL is serialize-parse roundtrippable, per whatwg/url@fdaa0e5.The breaking changes in this release are only to the Low-level URL Standard API. No actual URL parsing or serialization behavior has changed, and users of the
URL
andURLSearchParams
exports are not affected.These changes follow whatwg/url@fbaa03c.
cannotBeABaseURL
property.path
from always being an array of strings, to being either a single string or an array of strings."cannot-be-a-base-URL path"
parser state (i.e. value forstateOverride
) to"opaque path"
.serializePath(urlRecord)
export.hasAnOpaquePath(urlRecord)
export.The breaking changes in this release are to the API exported by the
whatwg-url/webidl2js-wrapper
module. In particular it now is based onwebidl2js
v17, which changes some of the exported function signatures, and changes the realms of any errors thrown on misuse.Made the host parser reject non-IPv4 domains that end in numbers, per whatwg/url@ab0e820.
Breaking changes:
Removed Node.js v10 support.
The
percentDecode()
export was renamedpercentDecodeBytes()
, and now returns aUint8Array
instead of a Node.jsBuffer
.Other changes:
The package's main module now exports the
percentDecodeString()
helper.The
punycode
andlodash
dependencies were removed.Make the
pathname
setter not mess up the URL's path state tracking when given the empty string, per whatwg/url@0672f2e.Made the
hostname
setter do nothing if the given string contains a colon, per whatwg/url@ec96993.Updated punycode processing to support Unicode v13.
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: