Gathering detailed insights and metrics for jest-environment-jsdom-global
Gathering detailed insights and metrics for jest-environment-jsdom-global
A Jest environment that allows you to configure jsdom
Installations
npm install jest-environment-jsdom-globalDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Min. Node Version
>= 14
Releases
10
v4.0.0: Jest 29 and EOL for Node 12
v4.0.0
Updated on Aug 30, 2022
v3.1.2: Bug fix
v3.1.2
Updated on May 20, 2022
v3.1.1: README updates
v3.1.1
Updated on Apr 30, 2022
v3.1.0: Jest 28 support
v3.1.0
Updated on Apr 30, 2022
v3.0.0: Jest 27 support + general hygiene
v3.0.0
Updated on Aug 27, 2021
v2.0.4: Update docs for JSDOM 16
v2.0.4
Updated on Jun 14, 2020
Languages
1
JavaScript
JavaScript (100%)
Developer
simon360
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
114 Stars
87 Commits
13 Forks
1 Watchers
23 Branches
5 Contributors
Updated on Jun 23, 2025
Maintainers
1
Package Meta Information
Latest Version
4.0.0
Package Id
jest-environment-jsdom-global@4.0.0
Unpacked Size
8.75 kB
Size
3.97 kB
File Count
6
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Peer Dependencies
1
Dev Dependencies
3
Jest environment for a globally-exposed JSDOM
Similar to the standard
jest-environment-jsdom, but exposesjsdomso that you can reconfigure it from your test suites.
For more information, see this discussion in the Jest repository.
Before installing, please check if you need this package, particularly in light of changes in Jest 28.
Installation and configuration
Install the package with yarn:
1yarn add --dev jest-environment-jsdom-global jest-environment-jsdom
or npm:
1npm install --save-dev jest-environment-jsdom-global jest-environment-jsdom
Then, add it to your Jest configuration:
1"jest": { 2 "testEnvironment": "jest-environment-jsdom-global" 3}
For more information, see the Jest documentation on testEnvironment.
Using JSDOM in your test suite
You can access the jsdom object globally in your test suite. For example, here's a test that changes the URL for your test environment (using reconfigure):
1describe("test suite", () => { 2 it("should not fail", () => { 3 jsdom.reconfigure({ 4 url: "https://www.example.com/", 5 }); 6 }); 7});
Frequently Asked Questions
Jest 28 update: is this package still useful?
As of Jest 28 (formal docs), you can provide options to JSDOM using inline comments in your tests. For example, to set the URL, you could write a test suite that looks like this:
/**
* @jest-environment jsdom
* @jest-environment-options {"url": "https://jestjs.io/"}
*/
test('use jsdom and set the URL in this test file', () => {
expect(window.location.href).toBe('https://jestjs.io/');
});
This may solve for many previous use cases for this package, and I'd suggest using this approach rather than using jest-environment-jsdom-global if it suffices for your needs.
Why can't I use Object.defineProperty?
Jest's browser environment is based on JSDOM. JSDOM used to allow you to use Object.defineProperty to update certain properties on window; in particular, you could change parts of window.location, or window.top, as you need to.
However, several years ago, JSDOM's API changed; the preferred way to mock window.location and its child properties is to use reconfigure. JSDOM 11 became the default back in Jest 22; as a result, tests that used Object.defineProperty may no longer work on certain properties of window.
Currently, Jest does not expose the JSDOM reconfigure method inside test suites. The jest-environment-jsdom-global package is meant to solve this problem: it adds jsdom as a global, so you can reconfigure it within your tests.
How can I mock window.location.href?
In your test, you can set the URL using:
1jsdom.reconfigure({ 2 url: "https://www.example.com/", 3});
How can I mock window.location.hash?
You need to provide a full URL, not just the hash. Similarly to above, you can do:
1jsdom.reconfigure({ 2 url: "https://www.example.com/#myHash", 3});
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
Found 2/11 approved changesets -- score normalized to 1
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/nodejs.yml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/simon360/jest-environment-jsdom-global/nodejs.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/nodejs.yml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/simon360/jest-environment-jsdom-global/nodejs.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/npmpublish.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/simon360/jest-environment-jsdom-global/npmpublish.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/npmpublish.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/simon360/jest-environment-jsdom-global/npmpublish.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/npmpublish.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/simon360/jest-environment-jsdom-global/npmpublish.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/npmpublish.yml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/simon360/jest-environment-jsdom-global/npmpublish.yml/main?enable=pin
- Info: 0 out of 6 GitHub-owned GitHubAction dependencies pinned
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/nodejs.yml:1
- Warn: no topLevel permission defined: .github/workflows/npmpublish.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 30 are checked with a SAST tool
Reason
11 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8
- Warn: Project is vulnerable to: GHSA-67hx-6x53-jw92
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-9c47-m6qq-7p4h
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
- Warn: Project is vulnerable to: GHSA-j8xg-fqg3-53r7
- Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
Score
2.9
/10
Last Scanned on 2025-06-30
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More