[PR #71] [MERGED] build(deps-dev): Bump jsdom from 26.1.0 to 27.0.0 #192

New issue

Closed

opened 2026-02-26 12:40:33 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 12:40:33 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE-Local/pull/71
Author: @dependabot[bot]
Created: 10/7/2025
Status: ✅ Merged
Merged: 10/7/2025
Merged by: @MickLesk

Base: main ← Head: dependabot/npm_and_yarn/jsdom-27.0.0

📝 Commits (1)

fd29e3b build(deps-dev): Bump jsdom from 26.1.0 to 27.0.0

📊 Changes

2 files changed (+221 additions, -69 deletions)

View changed files

📝 package-lock.json (+220 -68)
📝 package.json (+1 -1)

📄 Description

Bumps jsdom from 26.1.0 to 27.0.0.

Release notes

Sourced from jsdom's releases.

Version 27.0.0

Changes since 26.1.0

Node.js v20 is now the minimum supported version.

Added a variety of event constructors, even though we do not implement their associated specifications or ever fire them: BeforeUnloadEvent, BlobEvent, DeviceMotionEvent (omitting requestPermission()), DeviceOrientationEvent (omitting requestPermission()), PointerEvent, PromiseRejectionEvent, and TransitionEvent.

Added movementX and movementY to MouseEvent. (These are from the Pointer Lock specification, the rest of which is not implemented.)

Added customElements.getName(). (mash-graz)

Updated the virtual console:

"jsdomError" events are now documented, with specific type properties and other properties that depend on the type.

sendTo() was renamed to forwardTo().

The jsdomErrors option to forwardTo() can be used to control which errors are sent to the Node.js console. This replaces the previous omitJSDOMErrors boolean option.

"jsdomError"s for failed XMLHttpRequest fetches are no longer emitted.

The values that are printed when forwarding "jsdomError"s to the Node.js console are streamlined.

Switched our CSS selector engine from nwsapi to @asamuzakjp/dom-selector, closing over 20 selector-related bugs.

Upgraded tough-cookie, which now considers URLs like http://localhost/ to be secure contexts (per the spec), and thus will return Secure-flagged cookies for such URLs. (colincasey)

Upgraded cssstyle, which brings along many improvements and fixes to the CSSStyleDeclaration object and its properties.

Updated the user agent stylesheet to be derived from the HTML Standard, instead of from an old revision of Chromium.

Changed element.click() to fire a PointerEvent instead of a MouseEvent.

Changed certain events to be passive by default.

Changed the <input> element's pattern="" attribute to use the v regular expression flag, instead of u.

Fixed many specification conformance issues with the Window object, including named properties and changing various data properties to accessor properties.

Fixed document.createEvent() to accept a more correct set of event names.

Fixed the ElementInternals accessibility getters and setters. (They were introduced in v23.1.0, but due to inadequate test coverage never actually worked.)

Fixed using Object.defineProperty() on certain objects, such as HTMLSelectElement instances.

Fixed jsdom.reconfigure({ url }) not updating document.baseURI or properties derived from it. (This regressed in v26.1.0.)

Fixed CSS system colors, as well as the initial, inherit, and unset keywords, to resolve correctly. (asamuzaK)

Fixed CSS display style resolution. (asamuzaK)

Changes since 27.0.0-beta.3

Upgraded cssstyle, which brings along various CSS parsing fixes.

Version 27.0.0-beta.3

Breaking change: upgraded tough-cookie, which now considers URLs like http://localhost/ to be secure contexts (per the spec), and thus will return Secure-flagged cookies for such URLs. (colincasey)

Added customElements.getName(). (mash-graz)

Changed the <input> element's pattern="" attribute to use the v regular expression flag, instead of u.

Fixed jsdom.reconfigure({ url }) not updating document.baseURI or properties derived from it. This regressed in v26.1.0.

Fixed CSS system colors, as well as the initial, inherit, and unset keywords, to resolve correctly. This is especially important since the change in v27.0.0-beta.1 to use system colors in the user agent stylesheet. (asamuzaK)

Fixed CSS background property parsing and serialization. (asamuzaK)

Fixed CSS color parsing and serialization inside of gradients. (asamuzaK)

Fixed CSS display style resolution. (asamuzaK)

Upgraded @asamuzakjp/dom-selector, which notably fixed repeated use of the :scope selector. (asamuzaK)

Version 27.0.0-beta.2

Significantly improved specification conformance for the Window object, including named properties and changing various data properties to accessor properties. This is not likely to be breaking, but since it's a complex change to such a core object, we're happy to do another beta testing release with this included before graduating the v27 line to stable.

Additionally, updated cssstyle to v4.4.0, which brings along various conformance fixes to the CSSStyleDeclaration object and its properties.

Version 27.0.0-beta.1

Breaking changes:

... (truncated)

Changelog

Sourced from jsdom's changelog.

27.0.0

Commits

f2a505d Version 27.0.0
ab384d4 Update dependencies and dev dependencies
ff31107 Add passing :nth-child() in shadow DOM regresssion test
4e92a8e Add passing :scope() in :not() regression test
c3d6940 Version 27.0.0-beta.3
8073bae Use "v" instead of "u" for the pattern="" attribute
d77ffd0 Implement customElements.getName()
ac385f9 Fix reconfigure() not updating base URL caches
3ccd5de Update tough-cookie to v6
c2de8bd Address CSS regressions in v27 beta
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE-Local/pull/71 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 10/7/2025 **Status:** ✅ Merged **Merged:** 10/7/2025 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/jsdom-27.0.0` --- ### 📝 Commits (1) - [`fd29e3b`](https://github.com/community-scripts/ProxmoxVE-Local/commit/fd29e3b14581c6945f7d67ef7305209f2e713af8) build(deps-dev): Bump jsdom from 26.1.0 to 27.0.0 ### 📊 Changes **2 files changed** (+221 additions, -69 deletions) <details> <summary>View changed files</summary> 📝 `package-lock.json` (+220 -68) 📝 `package.json` (+1 -1) </details> ### 📄 Description Bumps [jsdom](https://github.com/jsdom/jsdom) from 26.1.0 to 27.0.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jsdom/jsdom/releases">jsdom's releases</a>.</em></p> <blockquote> <h2>Version 27.0.0</h2> <h3>Changes since 26.1.0</h3> <ul> <li>Node.js v20 is now the minimum supported version.</li> <li>Added a variety of event constructors, even though we do not implement their associated specifications or ever fire them: <code>BeforeUnloadEvent</code>, <code>BlobEvent</code>, <code>DeviceMotionEvent</code> (omitting <code>requestPermission()</code>), <code>DeviceOrientationEvent</code> (omitting <code>requestPermission()</code>), <code>PointerEvent</code>, <code>PromiseRejectionEvent</code>, and <code>TransitionEvent</code>.</li> <li>Added <code>movementX</code> and <code>movementY</code> to <code>MouseEvent</code>. (These are from the <a href="https://w3c.github.io/pointerlock/">Pointer Lock</a> specification, the rest of which is not implemented.)</li> <li>Added <code>customElements.getName()</code>. (mash-graz)</li> <li>Updated the <a href="https://github.com/jsdom/jsdom/blob/ab384d4e381eb6bb99ade4146698d35167b54837/README.md#virtual-consoles">virtual console</a>: <ul> <li><code>"jsdomError"</code> events are now documented, with specific <code>type</code> properties and other properties that depend on the type.</li> <li><code>sendTo()</code> was renamed to <code>forwardTo()</code>.</li> <li>The <code>jsdomErrors</code> option to <code>forwardTo()</code> can be used to control which errors are sent to the Node.js console. This replaces the previous <code>omitJSDOMErrors</code> boolean option.</li> <li><code>"jsdomError"</code>s for failed <code>XMLHttpRequest</code> fetches are no longer emitted.</li> <li>The values that are printed when forwarding <code>"jsdomError"</code>s to the Node.js console are streamlined.</li> </ul> </li> <li>Switched our CSS selector engine from <a href="https://www.npmjs.com/nwsapi"><code>nwsapi</code></a> to <a href="https://www.npmjs.com/package/@asamuzakjp/dom-selector"><code>@asamuzakjp/dom-selector</code></a>, closing over 20 selector-related bugs.</li> <li>Upgraded <a href="https://www.npmjs.com/package/tough-cookie"><code>tough-cookie</code></a>, which now considers URLs like <code>http://localhost/</code> to be secure contexts (per <a href="https://w3c.github.io/webappsec-secure-contexts/#is-origin-trustworthy">the spec</a>), and thus will return <code>Secure</code>-flagged cookies for such URLs. (colincasey)</li> <li>Upgraded <a href="https://github.com/jsdom/cssstyle"><code>cssstyle</code></a>, which brings along many improvements and fixes to the <code>CSSStyleDeclaration</code> object and its properties.</li> <li>Updated the user agent stylesheet to be derived from the HTML Standard, instead of from an old revision of Chromium.</li> <li>Changed <code>element.click()</code> to fire a <code>PointerEvent</code> instead of a <code>MouseEvent</code>.</li> <li>Changed certain events to be passive by default.</li> <li>Changed the <code><input></code> element's <code>pattern=""</code> attribute to use the <code>v</code> regular expression flag, instead of <code>u</code>.</li> <li>Fixed many specification conformance issues with the <code>Window</code> object, including named properties and changing various data properties to accessor properties.</li> <li>Fixed <code>document.createEvent()</code> to accept a more correct set of event names.</li> <li>Fixed the <code>ElementInternals</code> accessibility getters and setters. (They were introduced in v23.1.0, but due to inadequate test coverage never actually worked.)</li> <li>Fixed using <code>Object.defineProperty()</code> on certain objects, such as <code>HTMLSelectElement</code> instances.</li> <li>Fixed <code>jsdom.reconfigure({ url })</code> not updating <code>document.baseURI</code> or properties derived from it. (This regressed in v26.1.0.)</li> <li>Fixed CSS system colors, as well as the <code>initial</code>, <code>inherit</code>, and <code>unset</code> keywords, to resolve correctly. (asamuzaK)</li> <li>Fixed CSS <code>display</code> style resolution. (asamuzaK)</li> </ul> <h3>Changes since 27.0.0-beta.3</h3> <ul> <li>Upgraded <code>cssstyle</code>, which brings along various CSS parsing fixes.</li> </ul> <h2>Version 27.0.0-beta.3</h2> <ul> <li>Breaking change: upgraded <code>tough-cookie</code>, which now considers URLs like <code>http://localhost/</code> to be secure contexts (per <a href="https://w3c.github.io/webappsec-secure-contexts/#is-origin-trustworthy">the spec</a>), and thus will return <code>Secure</code>-flagged cookies for such URLs. (colincasey)</li> <li>Added <code>customElements.getName()</code>. (mash-graz)</li> <li>Changed the <code><input></code> element's <code>pattern=""</code> attribute to use the <code>v</code> regular expression flag, instead of <code>u</code>.</li> <li>Fixed <code>jsdom.reconfigure({ url })</code> not updating <code>document.baseURI</code> or properties derived from it. This regressed in v26.1.0.</li> <li>Fixed CSS system colors, as well as the <code>initial</code>, <code>inherit</code>, and <code>unset</code> keywords, to resolve correctly. This is especially important since the change in v27.0.0-beta.1 to use system colors in the user agent stylesheet. (asamuzaK)</li> <li>Fixed CSS <code>background</code> property parsing and serialization. (asamuzaK)</li> <li>Fixed CSS color parsing and serialization inside of gradients. (asamuzaK)</li> <li>Fixed CSS <code>display</code> style resolution. (asamuzaK)</li> <li>Upgraded <code>@asamuzakjp/dom-selector</code>, which notably fixed repeated use of the <code>:scope</code> selector. (asamuzaK)</li> </ul> <h2>Version 27.0.0-beta.2</h2> <p>Significantly improved specification conformance for the <code>Window</code> object, including named properties and changing various data properties to accessor properties. This is not likely to be breaking, but since it's a complex change to such a core object, we're happy to do another beta testing release with this included before graduating the v27 line to stable.</p> <p>Additionally, updated <a href="https://github.com/jsdom/cssstyle"><code>cssstyle</code></a> to v4.4.0, which brings along various conformance fixes to the <code>CSSStyleDeclaration</code> object and its properties.</p> <h2>Version 27.0.0-beta.1</h2> <p>Breaking changes:</p>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/jsdom/jsdom/blob/main/Changelog.md">jsdom's changelog</a>.</em></p> <blockquote> <h2>27.0.0</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jsdom/jsdom/commit/f2a505d5b8a91d8deb29847b2b028c334aec53df"><code>f2a505d</code></a> Version 27.0.0</li> <li><a href="https://github.com/jsdom/jsdom/commit/ab384d4e381eb6bb99ade4146698d35167b54837"><code>ab384d4</code></a> Update dependencies and dev dependencies</li> <li><a href="https://github.com/jsdom/jsdom/commit/ff31107eea10a85d6934701d5dc557e28122d69a"><code>ff31107</code></a> Add passing :nth-child() in shadow DOM regresssion test</li> <li><a href="https://github.com/jsdom/jsdom/commit/4e92a8e7722b49f71fac0214301bcc2621d1fdc2"><code>4e92a8e</code></a> Add passing :scope() in :not() regression test</li> <li><a href="https://github.com/jsdom/jsdom/commit/c3d69402eb9b8c5ce135f760a8e87aff989daca9"><code>c3d6940</code></a> Version 27.0.0-beta.3</li> <li><a href="https://github.com/jsdom/jsdom/commit/8073baecb4a6f288713c953bea3c7776f8c29d01"><code>8073bae</code></a> Use "v" instead of "u" for the pattern="" attribute</li> <li><a href="https://github.com/jsdom/jsdom/commit/d77ffd040cdf2ac0d0bbaf52edb5e544f225b037"><code>d77ffd0</code></a> Implement customElements.getName()</li> <li><a href="https://github.com/jsdom/jsdom/commit/ac385f9484e8f24d1c354f3083a25a7b80cf4866"><code>ac385f9</code></a> Fix reconfigure() not updating base URL caches</li> <li><a href="https://github.com/jsdom/jsdom/commit/3ccd5dea4878e1d7964b35d90049086995149881"><code>3ccd5de</code></a> Update tough-cookie to v6</li> <li><a href="https://github.com/jsdom/jsdom/commit/c2de8bd1553e5ca50823a7fa5be385947d7f6dba"><code>c2de8bd</code></a> Address CSS regressions in v27 beta</li> <li>Additional commits viewable in <a href="https://github.com/jsdom/jsdom/compare/26.1.0...27.0.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=jsdom&package-manager=npm_and_yarn&previous-version=26.1.0&new-version=27.0.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>