Skip to content
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

Closed
thymikee opened this issue Nov 24, 2017 · 4 comments · Fixed by #5622
Closed

Remove references to Node 4 compat #4947

thymikee opened this issue Nov 24, 2017 · 4 comments · Fixed by #5622

Comments

@thymikee
Copy link
Collaborator

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).

@genintho
Copy link
Contributor

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

@thymikee
Copy link
Collaborator Author

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

@satya164
Copy link
Contributor

I'm working on this one.

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants