6 people reported
All time, since Sep 21, including 3 thumbs-up on GitHub.
Vitest jsdom worker fails to start
“So something in jsdom@30.1.0 (vs 30.0.1, which works) trips Bun's EventTarget brand check when vitest installs its jsdom globals.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/bun/issues/5222/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Vitest jsdom worker fails to start with jsdom 30.1. Under Bun, "'addEventListener' called on an object that is not a valid instance of EventTarget"; jsdom 30.0 works.
Is this your bug?
File my report- Where
- node:vm
- Error text
TypeError: 'addEventListener' called on an object that is not a valid instance of EventTarget.- Versions
- 1.4.2 to 1.4.3
- Platforms
- Linux, macOS
- How bad
- Breaks a normal workflow. Most reports say it used to work.
Original reports3, newest first
- jsdom >= 30.1 breaks vitest jsdom environment: 'addEventListener' called on an object that is not a valid instance of EventTarget#45198
- node:vm: createContext(DONT_CONTEXTIFY) returns a different object than the context's globalThis (breaks jsdom >= 30.1)#45102
- vitest jsdom environment with jsdom 30.1.0: forks worker fails to start under bun (EventTarget brand check)#43671