-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove references to Node 4 compat #4947
Comments
Is Node 6 the new minima? I am asking to update the Troubleshooting section http://facebook.github.io/jest/docs/en/troubleshooting.html#compatibility-issues |
Yes and no. We decided to drop Node 4 support by default, because we upgraded to the new JSDOM. However, we still compile to Node 4-compliant code (but don't test it on CI though...), so it's possible to use it, but you need a custom test environment. See this issue for more details: #5211 |
I'm working on this one. |
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. |
Do you want to request a feature or report a bug?
Chore after Jest 22 release
There are multiple references, notes and tips regarding getting some features to work with Node4 and npm 2. Since we drop these in v22, it's safe to remove them after the release.
We should also make it clear and explicit in README, website and package.json's
engines
entry that Jest doesn't work with Node 4 (and npm 2).The text was updated successfully, but these errors were encountered: