fix: Rollback jsdom from 27.0.0 to 26.1.0

[xerial]

Summary

• Rollback jsdom from 27.0.0 to 26.1.0 to fix Scala.js test failures
• jsdom 27.0.0 introduced breaking API change (sendTo() → forwardTo())
• scala-js-env-jsdom-nodejs 1.1.0 still uses old sendTo() API
• Fix has been merged upstream but not yet released

Problem

PR #1316 upgraded jsdom from 26.1.0 to 27.0.0, which introduced a breaking change:

• VirtualConsole.sendTo() was renamed to forwardTo()
• This causes TypeError: (intermediate value).sendTo is not a function during Scala.js test execution
• The error occurs because scala-js-env-jsdom-nodejs 1.1.0 (last released May 2020) still uses the old API

Solution

Rollback jsdom to 26.1.0 until scala-js-env-jsdom-nodejs releases a new version with jsdom 27 support.

The fix has been merged in scala-js/scala-js-env-jsdom-nodejs#58 but not yet released.

Test plan

• Run Scala.js tests locally: ./sbt "langJS/test" - all 486 tests pass
• CI Scala.js tests should pass

Related Issues

Fixes #1316

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @xerial, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request implements a critical dependency rollback to address immediate test failures within the Scala.js environment. By reverting the jsdom library to a previous stable version, it restores compatibility with an unupdated upstream dependency, ensuring the continuous successful execution of Scala.js tests until a permanent fix is released.

Highlights

• Dependency Rollback: The jsdom dependency has been rolled back from version 27.0.0 to 26.1.0.
• Fix for Scala.js Tests: This rollback resolves Scala.js test failures caused by a breaking API change in jsdom 27.0.0, specifically the renaming of VirtualConsole.sendTo() to forwardTo().
• External Dependency Compatibility: The scala-js-env-jsdom-nodejs 1.1.0 library, which is a dependency, still relies on the old sendTo() API, leading to TypeError during test execution with jsdom 27.0.0.
• Temporary Solution: This change is a temporary measure until scala-js-env-jsdom-nodejs releases a new version that supports jsdom 27.0.0, for which a fix has already been merged upstream but not yet released.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly rolls back jsdom to version 26.1.0 to fix a breaking change introduced in v27.0.0 that was causing Scala.js tests to fail. The change is well-justified and clearly explained. I've added one suggestion to pin the dependency to the exact version for better stability and to prevent any unexpected issues from future patch releases. Overall, this is a solid fix.

[gemini-code-assist]

This is a good fix for the compatibility issue. To ensure future stability and prevent unexpected breakages from minor or patch updates within the 26.x series, it's a good practice to pin the dependency to the exact version that is known to work. This makes dependency resolution more deterministic.

Suggested change

	"jsdom": "^26.1.0",
	"jsdom": "26.1.0",