build(deps): bump @tootallnate/once, @graphql-codegen/cli and jsdom in /catalog

[dependabot]

Removes @tootallnate/once. It's no longer used after updating ancestor dependencies @tootallnate/once, @graphql-codegen/cli and jsdom. These dependencies need to be updated together.

Removes @tootallnate/once

Updates @graphql-codegen/cli from 1.21.8 to 6.1.2

Changelog

Sourced from @​graphql-codegen/cli's changelog.

6.1.2

Patch Changes

• #10590 e173e11 Thanks @​ya2s! - Fix GraphQL Config loading to forward nested extensions.codegen.config options when loading schemas/documents, matching codegen.ts behavior.

6.1.1

Patch Changes

• #10569 8cb7d43 Thanks @​etr2460! - fix(graphql-codegen-cli): Don't hang when 0 CPUs are found

  Fixes generation when 0 CPUs are returned by os.cpus(), which occurs in sandbox environments.

6.1.0

Minor Changes

• #10510 9e70bcb Thanks @​nickmessing! - add importExtension configuration option

Patch Changes

• Updated dependencies [9e70bcb]:
  • @​graphql-codegen/plugin-helpers@​6.1.0
  • @​graphql-codegen/client-preset@​5.2.0

6.0.2

Patch Changes

• #10430 aad7f03 Thanks @​renovate! - dependencies updates:
  • Updated dependency @graphql-tools/github-loader@^9.0.0 ↗︎ (from ^8.0.0, in dependencies)
  • Updated dependency @graphql-tools/url-loader@^9.0.0 ↗︎ (from ^8.0.0, in dependencies)
• Updated dependencies []:
  • @​graphql-codegen/client-preset@​5.1.2

6.0.1

Patch Changes

• #10468 cb1b9d9 Thanks @​eddeee888! - In watch mode, do not write output on failure

  Previously, on partial or full failure, watch mode still write to output. However, since the output'd be an empty array, it will then call removeStaleFiles internally to remove all previously generated files.

  This patch puts a temporary fix to avoid writing output on any failure to fix the described behaviour.

  This also means the config.allowPartialOutputs does not work in watch mode for now.

6.0.0

... (truncated)

Commits

• 8ae0fdd chore(release): update monorepo packages versions (#10600)
• e173e11 fix(cli): forward nested graphql-config loader options (#10590)
• 62c7618 chore(release): update monorepo packages versions (#10570)
• 8cb7d43 fix(graphql-codegen-cli): Don't hang when 0 CPUs are found (#10569)
• bec7e74 chore(release): update monorepo packages versions (#10513)
• 9e70bcb feat: add importExtension configuration option (#10510)
• 135ce4d chore(release): update monorepo packages versions (#10484)
• aad7f03 fix(deps): update graphql-tools (major) (#10430)
• c87b779 [CLI] Create watcher.run.spec to test actual running behaviour (#10474)
• ed30b56 chore(deps): update dependency vitest to v4 (#10475)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by theguild-bot, a new releaser for @​graphql-codegen/cli since your current version.

Updates jsdom from 22.1.0 to 28.1.0

Release notes

Sourced from jsdom's releases.

Version 28.1.0

• Added blob.text(), blob.arrayBuffer(), and blob.bytes() methods.
• Improved getComputedStyle() to account for CSS specificity when multiple rules apply. (asamuzaK)
• Improved synchronous XMLHttpRequest performance by using a persistent worker thread, avoiding ~400ms of setup overhead on every synchronous request after the first one.
• Improved performance of node.getRootNode(), node.isConnected, and event.dispatchEvent() by caching the root node of document-connected trees.
• Fixed getComputedStyle() to correctly handle !important priority. (asamuzaK)
• Fixed document.getElementById() to return the first element in tree order when multiple elements share the same ID.
• Fixed <svg> elements to no longer incorrectly proxy event handlers to the Window.
• Fixed FileReader event timing and fileReader.result state to more closely follow the spec.
• Fixed a potential hang when synchronous XMLHttpRequest encountered dispatch errors.
• Fixed compatibility with environments where Node.js's built-in fetch() has been used before importing jsdom, by working around undici v6/v7 incompatibilities.

Version 28.0.0

• Overhauled resource loading customization. See the new README for details on the new API.
• Added MIME type sniffing to <iframe> and <frame> loads.
• Regression: WebSockets are no longer correctly throttled to one connection per origin. This is a result of the bug at nodejs/undici#4743.
• Fixed decoding of the query components of <a> and <area> elements in non-UTF-8 documents.
• Fixed XMLHttpRequest fetches and WebSocket upgrade requests to be interceptable by the new customizable resource loading. (Except synchronous XMLHttpRequests.)
• Fixed the referrer of a document to be set correctly when redirects are involved; it is now the initiating page, not the last hop in the redirect chain.
• Fixed correctness bugs when passing ArrayBuffers or typed arrays to various APIs, where they would not correctly snapshot the data.
• Fixed require("url").parse() deprecation warning when using WebSockets.
• Fixed <iframe>, <frame>, and <img> (when canvas is installed) to fire load events, not error events, on non-OK HTTP responses.
• Fixed many small issues in XMLHttpRequest.

Version 27.4.0

• Added TextEncoder and TextDecoder.
• Improved decoding of HTML bytes by using the new @exodus/bytes package; it is now much more correct. (ChALkeR)
• Improved decoding of XML bytes to use UTF-8 more often, instead of sniffing for <meta charset> or using the parent frame's encoding.
• Fixed a memory leak when Ranges were used and then the elements referred to by those ranges were removed.

Version 27.3.0

• Improved CSS parsing and CSSOM object APIs via updates to @acemir/cssom. (acemir)

Version 27.2.0

• Added CSSGroupingRule, CSSNestedDeclarations, CSSConditionRule, CSSContainerRule, CSSScopeRule, CSSSupportsRule, CSSLayerBlockRule, and CSSLayerStatementRule to jsdom Windows. (acemir)
• Improved CSS parsing and CSSOM object APIs via updates to @acemir/cssom. (acemir)
• Fixed @import-ed stylesheets to be properly exposed to CSSOM, and not to overwrite the sheet created from the <link> or <style> element. (acemir)

Version 27.1.0

• Improved CSS parsing by switching to @acemir/cssom, including support for nested selectors, nested declarations, layer statements, and improved at-rule validation. (acemir)
• Fixed some selector cache invalidation issues where changes to attributes were not being picked up. (asamuzaK)
• Fixed package.json "engines" field to reflect the new minimum Node.js versions needed to run jsdom, as noted in the changelog for v27.0.1.

Version 27.0.1

This release inadvertently raised the minimum Node.js version from v20.0.0 to v20.19.0+, v22.12.0+, v24.0.0+. (This happened via a dependency update.) This probably should have been a breaking (major) change, instead of happening in a patch version, since it prevents using earlier Node.js versions.

After further testing, we found that most of our development dependencies also require these versions, and so it's not feasible for the jsdom project to support earlier Node.js versions. (For example, our testing frameworks will not run on them.) If you need to use such earlier versions, or otherwise are working in an environment which gives related errors such as ERR_REQUIRE_ESM, then please stick with the v26.1.0 release of jsdom. (Noting, of course, that such versions are unsupported, and we will not respond to bug reports opened against them.)

Subsequent jsdom releases will explicitly require these minimum Node.js versions, and will have CI testing to ensure that the minimum version is not accidentally raised again.

... (truncated)

Changelog

Sourced from jsdom's changelog.

28.1.0

• Added blob.text(), blob.arrayBuffer(), and blob.bytes() methods.
• Improved getComputedStyle() to account for CSS specificity when multiple rules apply. (asamuzaK)
• Improved synchronous XMLHttpRequest performance by using a persistent worker thread, avoiding ~400ms of setup overhead on every synchronous request after the first one.
• Improved performance of node.getRootNode(), node.isConnected, and event.dispatchEvent() by caching the root node of document-connected trees.
• Fixed getComputedStyle() to correctly handle !important priority. (asamuzaK)
• Fixed document.getElementById() to return the first element in tree order when multiple elements share the same ID.
• Fixed <svg> elements to no longer incorrectly proxy event handlers to the Window.
• Fixed FileReader event timing and fileReader.result state to more closely follow the spec.
• Fixed a potential hang when synchronous XMLHttpRequest encountered dispatch errors.
• Fixed compatibility with environments where Node.js's built-in fetch() has been used before importing jsdom, by working around undici v6/v7 incompatibilities.

28.0.0

• Overhauled resource loading customization. See the new README for details on the new API.
• Added MIME type sniffing to <iframe> and <frame> loads.
• Regression: WebSockets are no longer correctly throttled to one connection per origin. This is a result of the bug at nodejs/undici#4743.
• Fixed decoding of the query components of <a> and <area> elements in non-UTF-8 documents.
• Fixed XMLHttpRequest fetches and WebSocket upgrade requests to be interceptable by the new customizable resource loading. (Except synchronous XMLHttpRequests.)
• Fixed the referrer of a document to be set correctly when redirects are involved; it is now the initiating page, not the last hop in the redirect chain.
• Fixed correctness bugs when passing ArrayBuffers or typed arrays to various APIs, where they would not correctly snapshot the data.
• Fixed require("url").parse() deprecation warning when using WebSockets.
• Fixed <iframe>, <frame>, and <img> (when canvas is installed) to fire load events, not error events, on non-OK HTTP responses.
• Fixed many small issues in XMLHttpRequest.

27.4.0

• Added TextEncoder and TextDecoder.
• Improved decoding of HTML bytes by using the new @exodus/bytes package; it is now much more correct. (ChALkeR)
• Improved decoding of XML bytes to use UTF-8 more often, instead of sniffing for <meta charset> or using the parent frame's encoding.
• Fixed a memory leak when Ranges were used and then the elements referred to by those ranges were removed.

27.3.0

• Improved CSS parsing and CSSOM object APIs via updates to @acemir/cssom. (acemir)

27.2.0

• Added CSSGroupingRule, CSSNestedDeclarations, CSSConditionRule, CSSContainerRule, CSSScopeRule, CSSSupportsRule, CSSLayerBlockRule, and CSSLayerStatementRule to jsdom Windows. (acemir)
• Improved CSS parsing and CSSOM object APIs via updates to @acemir/cssom. (acemir)
• Fixed @import-ed stylesheets to be properly exposed to CSSOM, and not to overwrite the sheet created from the <link> or <style> element. (acemir)

27.1.0

• Improved CSS parsing by switching to @acemir/cssom, including support for nested selectors, nested declarations, layer statements, and improved at-rule validation. (acemir)
• Fixed some selector cache invalidation issues where changes to attributes were not being picked up. (asamuzaK)
• Fixed package.json "engines" field to reflect the new minimum Node.js versions needed to run jsdom, as noted in the changelog for v27.0.1.

27.0.1

... (truncated)

Commits

• 12949b5 Version 28.1.0
• ce4c58f Apply CSS specificity when computing styles
• 7ed55a0 Skip single-byte-decoder encoding tests on Node 20
• f3b1973 Generalize node version conditions in test expectations
• 853c596 Rewrite getElementById ID caching for tree-order correctness
• 5fbfde6 Fix potential sync XHR worker hang from unhandled dispatch errors
• 82df38f Cache the root node for document-connected trees
• ed7c5c0 Add documentation comment to create-event-accessor.js
• b4562e9 Simplify Window.js installEventHandlers
• 7da340f Centralize "determine the target of an event handler"
• Additional commits viewable in compare view

Install script changes

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

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 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Greptile Summary

This dependabot PR updates @graphql-codegen/cli from v1.21.8 to v6.1.2, jsdom from v22.1.0 to v28.1.0, and removes the now-unused transitive dependency @tootallnate/once.

Key finding:

• jsdom v28.1.0 requires Node.js ^20.19.0 || ^22.12.0 || >=24.0.0, but the project's engines.node field still declares only "20", which allows any 20.x release including 20.0.0–20.18.x. The engines constraint should be tightened to prevent test failures on incompatible Node versions.

Confidence Score: 2/5

• The PR introduces a version constraint mismatch that will break test execution on Node 20.0–20.18.
• One actionable issue identified: jsdom v28.1.0 requires Node.js ^20.19.0 || ^22.12.0 || >=24.0.0, but the engines.node field permits any Node 20.x, including incompatible earlier minors. This will cause test failures on those versions. The fix is straightforward (update the engines field), but the issue must be resolved before merging.
• catalog/package.json — requires engines.node update to match jsdom v28's minimum version requirement.

_{Last reviewed commit: 124ba76}

[greptile-apps]

Additional Comments (1)

catalog/package.json, line 12
jsdom v28.1.0 requires Node.js ^20.19.0 || ^22.12.0 || >=24.0.0 (as noted in the v27.0.1 release notes). However, the engines.node field declares only "20", which permits Node 20.0.0–20.18.x. Test environments on those earlier minor versions will fail.

Update engines to enforce the newer minimum:

  "engines": {
    "npm": "10",
    "node": "^20.19.0 || ^22.12.0 || >=24.0.0"
  },