jsdom 27.0.0 changes method name (sendTo -> forwardTo)

[raquo]

Getting this when I tried to bump jsdom to 27.0.1:

sbt:Laminar> test
...laminar/target/scalajs-bundler-jsdom/codeWithJSDOMContext.js:9
      .sendTo(console, { omitJSDOMErrors: true });

relevant jsdom changelog

relevant scalajs-bundler code

Currently we do:

var virtualConsole = new jsdom.VirtualConsole()
  .sendTo(console, { omitJSDOMErrors: true });

I haven't tested this, but I guess we should do something like this instead:

var virtualConsoleObj = new jsdom.VirtualConsole();
var virtualConsole = (typeof virtualConsoleObj.forwardTo === "function")
  ? virtualConsoleObj.forwardTo(console, { jsdomErrors: "none" }) // jsdom 27.0.0+
  : virtualConsoleObj.sendTo(console, { omitJSDOMErrors: true });

Not 100% sure which of the new jsdomErrors values is desired. The various options are explained at the bottom of jsdom virtual consoles doc section

[sjrd]

See https://github.com/scala-js/scala-js-env-jsdom-nodejs/releases/tag/v1.1.1 . You can bump that dependency to get the fix.

[unarist]

@sjrd scalajs-bundler uses its own fork of JSDOMNodeJSEnv instead of depending on scala-js-env-jsdom-nodejs.

scalajs-bundler/sbt-scalajs-bundler/src/main/scala/scalajsbundler/JSDOMNodeJSEnv.scala

Lines 16 to 17 in 2d9cbce

	// HACK Copy of Scala.js’ JSDOMNodeJSEnv. The only change is the ability to pass the directory in which jsdom has been installed
	class JSDOMNodeJSEnv(config: JSDOMNodeJSEnv.Config) extends JSEnv {

Can we get new release of scalajs-bundler with the fix, or merge into upstream? (I'm not sure how it's hard though)