Update dependency jsdom to v25 #46
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 contains the following updates:
^23.0.1->^25.0.0Release Notes
jsdom/jsdom (jsdom)
v25.0.1Compare Source
tough-cookie, which no longer prints a deprecation warning.v25.0.0Compare Source
This major release changes the prototype of a jsdom's
EventTarget.prototypeto point to theObject.prototypeinside the jsdom, instead of pointing to the Node.jsObject.prototype. Thus, the prototype chain ofWindowstays entirely within the jsdom, never crossing over into the Node.js realm.This only occurs when
runScriptsis set to non-default values of"dangerously"or"outside-only", as with the default value, there is no separateObject.prototypeinside the jsdom.This will likely not impact many programs, but could cause some changes in
instanceofbehavior, and so out of an abundance of caution, we're releasing it as a new major version.v24.1.3Compare Source
postMessage()that were done as a bare property (i.e.,postMessage()instead ofwindow.postMessage()).v24.1.2Compare Source
inoperator applied toEventTargetmethods, e.g.'addEventListener' in window, which only appeared in Node.js ≥22.5.0. (legendecas)blur(): it no longer firesfocusandfocusinon theDocument, andblurandfocusoutno longer have theirrelatedTargetproperty set. (asamuzaK)v24.1.1Compare Source
selectionchangeevent on theDocumentobject. (piotr-oles)v24.1.0Compare Source
getSetCookie()method to theHeadersclass. (ushiboy)Object.prototype, like"constructor"or"toString".rweb-cssom, which can now parse additional CSS constructs.v24.0.0Compare Source
This release reverts our selector engine back to
nwsapi. As discussed in #3659, the performance regressions from@asamuzakjp/dom-selectorturned out to be higher than anticipated. In the future, we can revisit@asamuzakjp/dom-selectorafter it reachesnwsapi's performance on the two real-world benchmarks provided by the community.Since reverting to
nwsapicauses 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.v23.2.0Compare Source
This release switches our CSS selector engine from
nwsapito@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-selectoris appreciated, and feel free to open an issue if this has had a significant impact on your project.v23.1.0Compare Source
ElementInternals, including theshadowRootgetter 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.valueAsANumbersetter to handleNaNcorrectly. (alexandertrefz)cssstylewhich contains several bug fixes.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.