[Snyk] Upgrade jsdom from 11.11.0 to 24.0.0 #13
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.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade jsdom from 11.11.0 to 24.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.
Warning: This is a major version upgrade, and may be a breaking change.
The recommended version fixes:
SNYK-JS-WS-1296835
Why? Confidentiality impact: None, Integrity impact: None, Availability impact: Low, Scope: Unchanged, Exploit Maturity: Proof of Concept, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00222, Social Trends: No, Days since published: 1077, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Medium, Package Popularity Score: 99, Impact: 2.35, Likelihood: 2.65, Score Version: V5
(*) Note that the real score may have changed since the PR was raised.
Release notes
Package name: jsdom
This release reverts our selector engine back to
nwsapi
. As discussed in #3659, the performance regressions from@ asamuzakjp/dom-selector
turned out to be higher than anticipated. In the future, we can revisit@ asamuzakjp/dom-selector
after it reachesnwsapi
's performance on the two real-world benchmarks provided by the community.Since reverting to
nwsapi
causes several functionality regressions, e.g. removing:has()
support, we've decided to make this a major version.Additionally:
input.maxLength
,input.minLength
,input.size
,progress.max
,tableCell.colSpan
,tableCell.rowSpan
,tableCol.span
,textArea.cols
,textArea.maxLength
,textArea.minLength
,textArea.rows
.This release switches our CSS selector engine from
nwsapi
to@ asamuzakjp/dom-selector
. The new engine is more actively maintained, and supports many new selectors: see the package's documentation for the full list. It also works better with shadow trees.There is a potential of a performance regression due to this change. In our stress test benchmark, which runs most of these 273 selectors against this 128 KiB document, the new engine completes the benchmark only 0.25x as fast. However, we're hopeful that in more moderate usage this will not be a significant issue. Any help speeding up
@ asamuzakjp/dom-selector
is appreciated, and feel free to open an issue if this has had a significant impact on your project.ElementInternals
, including theshadowRoot
getter and the string-valued ARIA properties. (zjffun)Element
.history.pushState()
andhistory.replaceState()
to follow the latest specification, notably with regards to how they handle empty string inputs and what new URLs are possible.input.valueAsANumber
setter to handleNaN
correctly. (alexandertrefz)cssstyle
which contains several bug fixes.canvas
peer dependency introduced in v23.0.0.whatwg-url
which integrates various additions to theURL
andURLSearchParams
objects.crypto.randomUUID()
. (jamesbvaughan)DOMRect
andDOMRectReadOnly
.AbortSignal.timeout()
.abortSignal.throwIfAborted()
.submitter
argument to theFormData
constructor. (jenseng)getComputedStyle()
's results for color-based properties, to resolve named colors and attempt to provide initial inheritance support. (hoekz-wwt)Window
's event handler properties (e.g.oncopy
,ontouchstart
, etc.) to reflect the latest list from the standard.DOMParser
-created documents to inherit their URL from the creating document.setRangeText()
used on<input>
and<textarea>
elements to calculate the new end index correctly. (pmstss)pageX
,pageY
,offsetX
, andoffsetY
onMouseEvent
s during dispatch. (jenseng)nwsapi
to v2.2.4, bringing along various fixes to our selector engine.jsdom.reconfigure()
to also adjust the URL as seen by the history API, so that e.g.history.replaceState(null, "")
would not mess up the URL. (jdufresne)location.hash = ""
to leave any#
in location.href.cssom
withrweb-cssom
, since the latter is maintained. (seanparmelee)x
,y
,pageX
,pageY
,offsetX
, andoffsetY
toMouseEvent
. (jenseng, ViniciusFXavier)unset
withgetComputedStyle()
. (jsnajdr)submitter
property toSubmitEvent
. (jenseng)MouseEvent
'sscreenX
andscreenY
to no longer coerce to integers, allowing fractional values. (jenseng)formEl.submit()
to not longer firesubmit
events. (jenseng)<link>
is removed. (jsnajdr)pointer-events
to inherit when used withgetComputedStyle()
. (jsnajdr)<script>
elements with nosrc=""
to no longer fireload
events. (t1ger2080)getComputedStyle()
to cache its results, which should make it much faster. (jsnajdr)Commit messages
Package name: jsdom
Compare
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:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs