npmpackage.info

Gathering detailed insights and metrics for react-tests-globals-setup

react-tests-globals-setup - 1.0.0 | npmpackage.info

react-tests-globals-setup

Setup a fake DOM and polyfill Intl so you can test react components in node

1.0.0

ISC

JavaScript

3.7

Installations

npm install react-tests-globals-setup

Developer Guide

BETA

Typescript

No

Module System

CommonJS

NPM Version

1.4.28 Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Languages

JavaScript

JavaScript (100%)

Developer

holidayextras

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

ISC License

2 Commits

7 Watchers

1 Branches

126 Contributors

Updated on Oct 06, 2015

Maintainers

View All 126 Contributors

Package Meta Information

Latest Version

1.0.0

Package Id

react-tests-globals-setup@1.0.0

Size

1.90 kB

NPM Version

1.4.28

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

intl jsdom

Dev Dependencies

make-up

react-tests-globals-setup

If you want to unit test react components with node & mocha, some globals need to be set up to make the environment more browser-like.

This will set up those globals.

The current version of this module uses a fake DOM provided by jsdom@3, which works with node 0.10 and 0.12. A future version will use newer jsdom and require node 4.

Usage

npm install react-tests-globals-setup --save-dev

Then add it as an argument to mocha, probably in your package.json:

  "scripts": {
    "test": "mocha --require react-tests-globals-setup"
  }

Or in mocha.opts

--require react-tests-globals-setup

Testing

npm test

## Linting

npm run lint

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

License

Determines if the project has defined a license.

5

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

Score

3.7

/10

Last Scanned on 2025-07-07

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