Skip to content

fix(ci): use Node 22 for jsdom 30 compatibility - #8

Merged
HecFranco merged 1 commit into
mainfrom
fix/jsdom-30-node-22-ci
Sep 3, 2026
Merged

fix(ci): use Node 22 for jsdom 30 compatibility#8
HecFranco merged 1 commit into
mainfrom
fix/jsdom-30-node-22-ci

Conversation

@HecFranco

Copy link
Copy Markdown
Contributor

Summary

  • Bump Node.js from 20 to 22 in CI and Dependabot workflows
  • Align package.json engines with undici 8.x / jsdom 30 requirement (>=22.19.0)

Root cause

jsdom 30 depends on undici 8.x, which calls worker_threads.markAsUncloneable at module load time. That API exists only from Node 22.10+, so vitest workers crashed on Node 20 before collecting tests (webidl.util.markAsUncloneable is not a function).

Test plan

  • TypeScript tests job passes on Node 22
  • Full CI green

Made with Cursor

jsdom 30 pulls undici 8.x, which requires worker_threads.markAsUncloneable
available only from Node 22.10+. CI was pinned to Node 20, causing vitest
to fail before collecting any tests.
@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown

@coderabbitai review

@HecFranco
HecFranco merged commit 4cf72dc into main Sep 3, 2026
20 checks passed
@HecFranco
HecFranco deleted the fix/jsdom-30-node-22-ci branch September 3, 2026 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant