Hi,
Im using your package to fix the issue described here:
https://github.com/testing-library/dom-testing-library/releases/tag/v7.0.0

If I use the library like this all is grate"
"test": "react-scripts test --env=jest-environment-jsdom-sixteen"

How ever when trying to include it in the jest config as so:

"jest": {
    "testEnvironment": "jest-environment-jsdom-sixteen"
  },

I see no effect as if the testEnvironment is ignored.

And I get the same error as described in the link to the dom-testing-library release.

Thanks :)

My project needs jest26 to run, but with the latest version of jest-environment-jsdom-sixteen it has multiple versions of jest packages installed:

├─ [email protected]
│  ├─ @jest/[email protected]
│  ├─ @jest/[email protected]
│  ├─ @jest/[email protected]
│  ├─ @jest/[email protected]
│  ├─ @jest/[email protected]
│  ├─ [email protected]
│  ├─ [email protected]
│  └─ [email protected]

Since JSDOM 16 is already shipped with Jest, is there any reason to keep this library, or could it be removed?

It'd be great to get them all aligned 🙏

I experienced following errors when run my tests on Node v. 10.13.0: ReferenceError: window is not defined and ReferenceError: describe is not defined. It is the same errors as for jest-environment-node described in jestjs/jest#9453, but I think it is worth to mention this issue here.

This behavior introduced with implementation of getVmContext() method and does not affect jest-environment-jsdom. It it caused by a bug in old versions of Node nodejs/node#23206 and fixed in Node v. 10.14.2.

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

• CircleCI
• Travis CI
• Buildkite
• CodeShip
• Azure Pipelines
• TeamCity
• Buddy
• AppVeyor
  But Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

HI @SimenB,

I was trying to start using this package and I see the NodeJS version 11 is not supported on engines, any specific reason for this?