jest-environment-jsdom in node < 6

[ljharb]

By requiring jsdom v10 and above in v22, node 6 is required. This means jest v22 and above can't be used to test node packages that support node 4, which is still in LTS.

Could jest-environment-jsdom be pegged at jsdom@v9, to avoid this breakage?

[ljharb]

#4770 seems to suggest it's intentional, but that mean that jest isn't useful on a published package, most of which support multiple versions of node (typically all LTS versions at least).

What's the value in aggressively dropping support for older node versions? (@cpojer)

[thymikee]

@ljharb you can use custom environment with jsdom 9, see: #5122

[ljharb]

@thymikee i read that thread and I'm not sure how to use jest 22 with jsdom 9. can you elaborate? the "node" test environment doesn't help me run tests with jsdom.

[thymikee]

In #5122 we made sure Jest is being able to run (or rather compile itself) on Node 4.

Here's a brief doc on how to create a custom environment. What you need to do, is to import jsdom 9 there and use it accordingly, similarly to how it was done earlier.
It would be great to publish it as an npm module and reference it somewhere.

[cpojer]

What @thymikee said is correct. The main Jest installation doesn’t officially support node 4 any longer. However, you can build your own custom test environment with an older version of jsdom that should still work for you. Members from the community have stepped up to make Jest 22 work on node 4 again. Please note that Jest tends to segfault on node 4, at least when running Jest’s own test suite, so there are definitely some issues in node 4 that you can avoid by upgrading.

If that doesn’t work for you, Jest 21 will keep working fine on node 4.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.