A superset of the JSDOM environment for Jest that respects Node.js globals.
npm install jest-fixed-jsdomA superset of the JSDOM environment for Jest that respects Node.js globals.
> [!WARNING]
> This package is never meant as a solution to anything. This is a workaround. Please consider testing browser code in the actual browser. You can do so both in Vitest and in Playwright at the moment.
When you use Jest with JSDOM you are getting a broken test environment. Some Node.js globals cease to exist (e.g. Request, Response, TextEncoder, TextDecoder, ReadableStream1), while others stop behaving correctly (e.g. Event, MessageEvent2, structuredClone()3). That is caused by jest-environment-jsdom and JSDOM relying on polyfills to implement standard APIs that have been available globally both in the browser and in Node.js for years.
Here's a piece of valid JavaScript that works in both the browser and Node.js but fails in Jest/JSDOM:
``js`
new TextEncoder().encode('hello')
`
ReferenceError: TextEncoder is not defined
We strongly believe that a valid JavaScript code must compile regardless of what test environment you are using. In fact, having a proper test environment is crucial to get any kind of value from your tests. Jest/JSDOM take that already working environment away from you.
We've built this project aims to fix that problem, restoring the global APIs that are present in both environments, providing better interoperability, stability, and consistent runtime behavior.
This project "fixes" the following global APIs, overriding whichever polyfills they have with respective Node.js globals:
- fetch()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
`sh`
npm i jest-fixed-jsdom --save-dev
In your jest.config.js, set the testEnvironment option to jest-fixed-jsdom:
`js`
// jest.config.js
module.exports = {
testEnvironment: 'jest-fixed-jsdom',
}
> You can use any other testEnvironmentOptions you need. Those will be forwarded to the underlying jest-environment-jsdom`.