Skip to content

chore(deps-dev): bump jsdom from 27.4.0 to 30.0.1 in /web - #629

Open
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/npm_and_yarn/web/jsdom-30.0.1
Open

chore(deps-dev): bump jsdom from 27.4.0 to 30.0.1 in /web#629
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/npm_and_yarn/web/jsdom-30.0.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 2, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps jsdom from 27.4.0 to 30.0.1.

Release notes

Sourced from jsdom's releases.

v30.0.1

  • Fixed getComputedStyle() with calc() and other functions throwing an exception, which regressed in v30.0.0. (@​asamuzaK)
  • Sped up up range operations on large documents (@​leonidaz)

v30.0.0

Breaking changes:

  • Node.js minimum version raised to ^22.22.2 || ^24.15.0 || >=26.0.0.

Other changes:

  • Added CSS.escape() and CSS.supports() functions. (@​asamuzaK)
  • Added 'background-position-x' and 'background-position-y' CSS properties. (@​olagokemills)
  • Fixed getComputedStyle() to convert length values into pixels. (@​asamuzaK)
  • Fixed CSS function serialization, e.g., in the return value of getPropertyValue(). (@​asamuzaK)
  • Fixed the type of error thrown by document.evaluate() (@​dokson)

v29.1.1

  • Fixed 'border-radius' computed style serialization. (@​asamuzaK)
  • Fixed computed style computation when using 'background-origin' and 'background-clip' CSS properties. (@​asamuzaK)
  • Significantly optimized initial calls to getComputedStyle(), before the cache warms up. (@​asamuzaK)

v29.1.0

  • Added basic support for the ratio CSS type. (@​asamuzaK)
  • Fixed getComputedStyle() sometimes returning outdated results after CSS was modified. (@​asamuzaK)

v29.0.2

  • Significantly improved and sped up getComputedStyle(). Computed value rules are now applied across a broader set of properties, and include fixes related to inheritance, defaulting keywords, custom properties, and color-related values such as currentcolor and system colors. (@​asamuzaK)
  • Fixed CSS 'background' and 'border' shorthand parsing. (@​asamuzaK)

v29.0.1

  • Fixed CSS parsing of 'border', 'background', and their sub-shorthands containing keywords or var(). (@​asamuzaK)
  • Fixed getComputedStyle() to return a more functional CSSStyleDeclaration object, including indexed access support, which regressed in v29.0.0.

v29.0.0

Breaking changes:

  • Node.js v22.13.0+ is now the minimum supported v22 version (was v22.12.0+).

Other changes:

  • Overhauled the CSSOM implementation, replacing the @acemir/cssom and cssstyle dependencies with fresh internal implementations built on webidl2js wrappers and the css-tree parser. Serialization, parsing, and API behavior is improved in various ways, especially around edge cases.
  • Added CSSCounterStyleRule and CSSNamespaceRule to jsdom Windows.
  • Added cssMediaRule.matches and cssSupportsRule.matches getters.
  • Added proper media query parsing in MediaList, using css-tree instead of naive comma-splitting. Invalid queries become "not all" per spec.
  • Added cssKeyframeRule.keyText getter/setter validation.
  • Added cssStyleRule.selectorText setter validation: invalid selectors are now rejected.
  • Added styleSheet.ownerNode, styleSheet.href, and styleSheet.title.
  • Added bad port blocking per the fetch specification, preventing fetches to commonly-abused ports.
  • Improved Document initialization performance by lazily initializing the CSS selector engine, avoiding ~0.5 ms of overhead per Document. (@​thypon)

... (truncated)

Commits
  • 6584485 30.0.1
  • 0c51df6 Update dependencies and dev dependencies
  • 32adb34 Bump @​asamuzakjp/dom-selector
  • 70f014a Speed up range operations on large documents
  • 250d7ee Partially fix getComputedStyle with calc()
  • 20a01fc 30.0.0
  • 8c8e583 Precompute WPT expectation matches
  • f32245c Bump Node.js floor and dependencies
  • 03ef23b Add background-position longhands
  • ded056f Test CSS.escape() with numeric IDs
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for jsdom since your current version.

Install script changes

This version modifies prepare script that runs during installation. Review the package contents before updating.

@dependabot @github

dependabot Bot commented on behalf of github Aug 2, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies, web. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot
dependabot Bot requested a review from meganetaaan as a code owner August 2, 2026 08:33
@dependabot dependabot Bot mentioned this pull request Aug 2, 2026
Closed
@github-actions

github-actions Bot commented Aug 2, 2026 •
edited
Loading

Copy link
Copy Markdown

Cloudflare PR preview

The preview build failure. No new deployment was published.

Open the failed workflow run. Any URL from an earlier comment is stale.

@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/web/jsdom-30.0.1 branch from 56b8052 to c3a5811 Compare August 9, 2026 00:06
@dependabot
chore(deps-dev): bump jsdom from 27.4.0 to 30.0.1 in /web
b33ab0c 
Bumps [jsdom](https://github.com/jsdom/jsdom) from 27.4.0 to 30.0.1.
- [Release notes](https://github.com/jsdom/jsdom/releases)
- [Commits](jsdom/jsdom@v27.4.0...v30.0.1)

---
updated-dependencies:
- dependency-name: jsdom
  dependency-version: 30.0.1
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/web/jsdom-30.0.1 branch from c3a5811 to b33ab0c Compare August 9, 2026 12:14
@meganetaaan

meganetaaan commented Aug 10, 2026

Copy link
Copy Markdown
Collaborator

Dependabot maintenance review

Scope reviewed: web dev dependency update only: jsdom ^27.4.0 → ^30.0.1, plus web/package-lock.json. No source-code changes were present.

Local verification:

  • cd /tmp/stackchan-dependabot-pr-629/web && node --version → v24.15.0
  • cd /tmp/stackchan-dependabot-pr-629/web && npm ci → failed
  • Simulated merge onto current develop, then cd web && npm ci → failed with the same dependency conflict

Finding: this update is currently blocked before tests can run. blockly@13.2.0 declares peer dependency jsdom@">=27.4.0 <30.0.0", while this PR installs jsdom@30.0.1. npm view blockly version peerDependencies --json currently reports latest blockly as 13.2.1 with the same <30.0.0 peer range, so there is no small safe companion blockly bump available right now.

Remote checks: failing (test-fast, test, web-visual, and Bundle web artifacts); GitHub logs were empty via gh run view --log-failed / per-job --log, but the local npm ci failure reproduces the blocker.

Decision: skipped; not approved or merged. Recommend waiting for Blockly to support jsdom 30, or closing/replacing this Dependabot PR with the latest jsdom 29.x line while Blockly still requires <30.

@meganetaaan

meganetaaan commented Aug 11, 2026

Copy link
Copy Markdown
Collaborator

Dependabot maintenance re-check

Scope reviewed: web dependency-only PR: jsdom ^27.4.0 → ^30.0.1, with web/package-lock.json. No source changes or suspicious mixed edits were present.

Local verification run today:

  • cd /tmp/stackchan-dependabot-pr-629/web && node --version → v24.15.0
  • cd /tmp/stackchan-dependabot-pr-629/web && npm --version → 11.7.0
  • cd /tmp/stackchan-dependabot-pr-629/web && npm ci → failed (ERESOLVE)
  • Simulated merge onto current live default branch develop, then cd /tmp/stackchan-dependabot-pr-629-merge/web && npm ci → failed with the same ERESOLVE
  • npm view blockly version peerDependencies --json → latest blockly is 13.2.1 and still declares jsdom >=27.4.0 <30.0.0

Finding: still blocked by an upstream peer-dependency conflict. This PR installs jsdom@30.0.1, while blockly@13.2.0 requires jsdom >=27.4.0 <30.0.0; the latest Blockly release does not yet relax that peer range. I did not use --force or --legacy-peer-deps because that would bypass the repository’s normal install gate.

Remote checks: failure by robust statusCheckRollup parsing. Failed checks remain test-fast, test, web-visual, and Bundle web artifacts. gh run view --log-failed returned no useful failed-job log output, but the local npm ci failure reproduces the blocker directly.

Decision: skipped; not approved and not merged. Recommend waiting for Blockly support for jsdom 30, or replacing this with the latest jsdom 29.x update while Blockly still requires <30.

@meganetaaan

meganetaaan commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator

Dependabot maintenance re-check

Scope reviewed: web dependency-only PR: jsdom ^27.4.0 → ^30.0.1, with web/package-lock.json. No source changes or suspicious mixed edits were present.

Repository state note: the live default branch is currently develop (the cron prompt mentioned dev/v1.0, which is stale), so I verified the simulated merge against develop.

Local verification run today:

  • cd /tmp/stackchan-dependabot-pr-629/web && node --version → v24.15.0
  • cd /tmp/stackchan-dependabot-pr-629/web && npm --version → 11.12.1
  • cd /tmp/stackchan-dependabot-pr-629/web && npm ci → failed (ERESOLVE)
  • Simulated merge onto current live default branch develop, then cd /tmp/stackchan-dependabot-pr-629-merge/web && npm ci → failed with the same ERESOLVE
  • npm view blockly version peerDependencies --json → latest blockly is 13.2.1 and still declares jsdom >=27.4.0 <30.0.0

Finding: still blocked by an upstream peer-dependency conflict. This PR installs jsdom@30.0.1, while blockly@13.2.0 requires jsdom >=27.4.0 <30.0.0; the latest Blockly release does not yet relax that peer range. I did not use --force or --legacy-peer-deps because that would bypass the repository’s normal install gate.

Remote checks: failure by robust statusCheckRollup parsing. Failed checks: test-fast, Bundle web artifacts, web-visual, test. Current mergeability: mergeStateStatus=UNSTABLE, mergeable=MERGEABLE, head=b33ab0c8049f01387c6d433e7505e599a83c9658. gh run view --log-failed returned no useful failed-job log output, but the local npm ci failure reproduces the blocker directly.

Decision: skipped; not approved and not merged. Recommend waiting for Blockly support for jsdom 30, or replacing this with the latest jsdom 29.x update while Blockly still requires <30.

@meganetaaan

meganetaaan commented Aug 13, 2026

Copy link
Copy Markdown
Collaborator

Dependabot maintenance re-check

Scope reviewed: web dependency-only PR: jsdom ^27.4.0 → ^30.0.1, with web/package-lock.json. No source changes or suspicious mixed edits were present.

Repository state note: live default branch is currently develop (the cron prompt mentioned dev/v1.0, which is stale), so I verified the simulated merge against develop.

Local verification run today:

  • cd /tmp/stackchan-dependabot-pr-629/web && node --version → v24.15.0
  • cd /tmp/stackchan-dependabot-pr-629/web && npm --version → 11.12.1
  • cd /tmp/stackchan-dependabot-pr-629/web && npm ci → failed before tests/builds could run
  • Simulated merge onto current origin/develop, then cd /tmp/stackchan-dependabot-pr-629-merge/web && npm ci → failed the same way
  • npm view blockly version peerDependencies --json → latest blockly@13.2.1 still declares jsdom >=27.4.0 <30.0.0
  • npm view jsdom version peerDependencies engines --json → latest jsdom@30.0.1, Node engines are compatible with the local Node version

Blocking finding: npm ci fails with an npm peer dependency conflict:

While resolving: blockly@13.2.0
Found: jsdom@30.0.1
Could not resolve dependency:
peer jsdom@">=27.4.0 <30.0.0" from blockly@13.2.0

This reproduces both on the raw Dependabot head and on a simulated merge with the current default branch, so it is not just a stale-base issue. Because the latest Blockly release still excludes jsdom 30, I did not force install with --force / --legacy-peer-deps or push an unrelated workaround.

Remote checks: current PR check rollup is failing (test-fast, web-visual, test, and Bundle web artifacts failed; other firmware bundle jobs succeeded or were skipped). gh run view --log-failed returned no useful failed-log output for the affected runs, but the local install reproduces the blocker clearly.

Decision: left unmerged. Recommended path is to wait for Blockly support for jsdom 30, or keep jsdom on the latest <30 line while Blockly's peer range remains capped.

@meganetaaan

meganetaaan commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

Dependabot maintenance re-check

Scope reviewed: web dependency-only PR: jsdom ^27.4.0 → ^30.0.1, plus web/package-lock.json. No source-code or suspicious mixed edits were present.

Repository state note: live default branch is currently develop (the cron prompt mentioned dev/v1.0, which is stale), so I verified the simulated merge against develop.

Local verification run today:

  • cd /tmp/stackchan-dependabot-pr-629/web && node --version → v24.15.0
  • cd /tmp/stackchan-dependabot-pr-629/web && npm --version → 11.12.1
  • cd /tmp/stackchan-dependabot-pr-629/web && npm ci → failed (ERESOLVE)
  • Simulated merge onto current develop, then cd web && node --version && npm --version && npm ci → failed with the same ERESOLVE peer dependency conflict
  • npm view blockly version peerDependencies --json → latest blockly@13.2.1 still declares jsdom >=27.4.0 <30.0.0
  • npm view jsdom version peerDependencies engines --json → latest jsdom@30.0.1; engines include Node ^22.22.2 || ^24.15.0 || >=26.0.0

Remote check state: not mergeable for automation. Current check rollup still has failures in Build Stack-chan Firmware/test-fast, Build Stack-chan Firmware/test, Build Stack-chan Firmware/web-visual, and Bundle Stack-chan Firmware/Bundle web artifacts.

Finding: this remains blocked by Blockly's peer range excluding jsdom@30.x. Because npm ci fails on both the raw Dependabot head and a simulated merge onto current develop, tests/builds cannot be reached safely. I did not use --force or --legacy-peer-deps.

Merge decision: skipped / not merged. Recommended path is to wait until Blockly supports jsdom@30, or have Dependabot target the latest allowed jsdom@29.x line while Blockly's peer range remains capped.

@meganetaaan

meganetaaan commented Aug 15, 2026

Copy link
Copy Markdown
Collaborator

Dependabot maintenance re-check

Scope reviewed: web dependency-only PR: jsdom ^27.4.0 → ^30.0.1, plus web/package-lock.json. No source-code changes or suspicious mixed edits were present.

Repository state note: live default branch is currently develop (the cron prompt mentioned dev/v1.0, which is stale), so I verified the simulated merge against develop.

Local verification run today:

  • cd /tmp/stackchan-dependabot-pr-629/web && node --version → v24.15.0
  • cd /tmp/stackchan-dependabot-pr-629/web && npm --version → 11.12.1
  • cd /tmp/stackchan-dependabot-pr-629/web && npm ci → failed (ERESOLVE)
  • Simulated merge onto current origin/develop, then cd /tmp/stackchan-dependabot-pr-629-merge/web && npm ci → failed with the same ERESOLVE peer dependency conflict
  • npm view blockly version peerDependencies --json → latest blockly@13.2.1 still declares jsdom >=27.4.0 <30.0.0
  • npm view jsdom@30.0.1 version engines peerDependencies --json → jsdom@30.0.1 requires Node ^22.22.2 || ^24.15.0 || >=26.0.0 and has optional canvas peer ^3.2.3

Remote check state: failure by statusCheckRollup; failed checks remain test-fast, test, web-visual, and Bundle web artifacts. mergeStateStatus is UNSTABLE.

Finding: still blocked by an upstream peer-dependency conflict. The repository currently has blockly@13.2.0, which requires jsdom >=27.4.0 <30.0.0; the latest available Blockly release (13.2.1) has the same peer range. I did not use --force or --legacy-peer-deps, and I did not push a workaround because that would bypass the package manager’s compatibility gate.

Merge decision: skipped / not merged. This PR should wait until Blockly publishes a release compatible with jsdom@30, or Dependabot opens a smaller compatible update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@meganetaaan meganetaaan Awaiting requested review from meganetaaan meganetaaan is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@meganetaaan