chore(deps): update dependency jsdom to v24 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
jsdom	^22.1.0 -> ^24.0.0

---

Release Notes

jsdom/jsdom (jsdom)

v24.1.1

Compare Source

• Fixed selection methods to trigger the selectionchange event on the Document object. (piotr-oles)

v24.1.0

Compare Source

• Added the getSetCookie() method to the Headers class. (ushiboy)
• Fixed the creation and parsing of elements with names from Object.prototype, like "constructor" or "toString".
• Updated rweb-cssom, which can now parse additional CSS constructs.

v24.0.0

Compare Source

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 reaches nwsapi'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:

• Small fixes to edge-case behavior of the following properties: input.maxLength, input.minLength, input.size, progress.max, tableCell.colSpan, tableCell.rowSpan, tableCol.span, textArea.cols, textArea.maxLength, textArea.minLength, textArea.rows.

v23.2.0

Compare Source

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.

v23.1.0

Compare Source

• Added an initial implementation of ElementInternals, including the shadowRoot getter and the string-valued ARIA properties. (zjffun)
• Added the string-valued ARIA attribute-reflecting properties to Element.
• Fixed history.pushState() and history.replaceState() to follow the latest specification, notably with regards to how they handle empty string inputs and what new URLs are possible.
• Fixed the input.valueAsANumber setter to handle NaN correctly. (alexandertrefz)
• Updated various dependencies, including cssstyle which contains several bug fixes.

v23.0.1

Compare Source

• Fix incorrect canvas peer dependency.

v23.0.0

Compare Source

---

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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@vue/[email protected]	environment, eval	+7	5.58 MB	yyx990803
npm/@vue/[email protected]	environment, eval, filesystem, unsafe	+10	7.84 MB	yyx990803
npm/[email protected]	Transitive: environment	+9	134 kB	baiwusanyu
npm/[email protected]	environment, filesystem Transitive: network, shell	+26	992 kB	antfu
npm/[email protected]	None	0	43.7 kB	sindresorhus
npm/[email protected]	environment, eval, filesystem	0	1.19 MB	zloirock
npm/[email protected]	environment Transitive: filesystem, shell	+1	50.3 kB	kentcdodds
npm/[email protected]	environment, filesystem Transitive: eval, shell, unsafe	+44	8.76 MB	eslintbot
npm/[email protected]	None	0	2.66 kB	antfu
npm/[email protected]	None	0	30.7 kB	baiwusanyu
npm/[email protected]	Transitive: environment, filesystem	+1	92 kB	ryanzim
npm/[email protected]	Transitive: environment	+6	220 kB	antfu
npm/[email protected]	Transitive: environment, filesystem, network, unsafe	+40	531 kB	phated
npm/[email protected]	None	0	8.13 kB	bevacqua

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Protestware/Troll package	npm/[email protected]	Note: This package prints a protestware console message on install regarding Ukraine for users with Russian language locale	orphan: npm/[email protected]
Install scripts	npm/[email protected]	Install script: postinstall Source: node -e "try{require('./_postinstall')}catch(e){}" || exit 0	orphan: npm/[email protected]
Install scripts	npm/[email protected]	Install script: postinstall Source: node install.js	orphan: npm/[email protected]
Install scripts	npm/[email protected]	Install script: install Source: node install.js	orphan: npm/[email protected]
Native code	npm/[email protected]	Location: Package overview	orphan: npm/[email protected]
Install scripts	npm/[email protected]	Install script: postinstall Source: node -e "try{require('./postinstall')}catch(e){}"	play/webpack/package.json pnpm-lock.yaml
Install scripts	npm/[email protected]	Install script: postinstall Source: node install.js	orphan: npm/[email protected]
Install scripts	npm/[email protected]	Install script: postinstall Source: node install.js	play/webpack/package.json pnpm-lock.yaml

View full report↗︎

Next steps

What is protestware?

This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function.

Consider that consuming this package my come along with functionality unrelated to its primary purpose.

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]