Support JSDOM

[itsezc]

What is the problem this feature would solve?

Currently DOM testing can be achieved, albeit through a third party library, while this is fine it'd be great if we can standardise this to some extent similar to Vite / Vitest's approach, by making this an easily configurable option.

What is the feature you are proposing to solve the problem?

For tests, I believe the DOM should automatically be added in where for instance the tsconfig.json contains DOM in the lib field, or alternatively a configuration option in bunfig.toml. This could also additionally be used to enable DOM matchers (related to #1825).

JSDOM is the obvious candidate, but other alternatives could be considered here, such as happy-dom. Although from my (limited) understanding, JSDOM remains prevalent with many testing libraries out there.

Related to #198 and #1825

What alternatives have you considered?

N/A

[colinhacks]

Hijacking this to serve as a tracking issue for JSDOM support.

Currently this is blocked on node-canvas which uses V8 C++ APIs internally.

[gitblit]

Adding a small failure sample here concerning vm.runInContext used by JSDOM. Same test works as expected on Node.

[niels-bosman]

I’d like to add that JSDOM support would not only enhance testing capabilities but also benefit applications that use JSDOM to convert XML data into a queryable DOM. Are there any plans to prioritize this in the short term?

[niels-bosman]

You are a hero @Jarred-Sumner

[coopbri]

You are a hero @Jarred-Sumner

Truly a god among men

Jarred: but bun wait, there's more