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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

testEnvironment configuration no longer finds "node" option. #11495

Closed
umbertix opened this issue May 31, 2021 · 2 comments
Closed

testEnvironment configuration no longer finds "node" option. #11495

umbertix opened this issue May 31, 2021 · 2 comments

Comments

@umbertix
Copy link

馃挜 Regression Report

testEnvironment configuration no longer finds "node" option (see image below).
Removing the option specificity and letting use the default, which is also node, works without a problem.
Still investigating what this might be coming from, I suspect yarn2, but I don't have any evidence to back this.

If anyone is having a similar issue any help would be much appreciated.

image

Last working version

Worked up to version: 27.0.1

Stopped working in version: 27.0.3

To Reproduce

Steps to reproduce the behavior: run jest

Expected behavior

Keep the same behaviour as last version and work without raising an error.

npx envinfo --preset jest

  System:
    OS: macOS 11.3.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
  Binaries:
    Node: 16.2.0 - /usr/local/bin/node
    Yarn: 2.4.1 - /usr/local/bin/yarn
    npm: 7.13.0 - /usr/local/bin/npm

@umbertix umbertix changed the title testEnvironment` configuration no longer finds "node" option. testEnvironment configuration no longer finds "node" option. May 31, 2021
@SimenB
Copy link
Member

SimenB commented May 31, 2021

#11452 (comment)

@SimenB SimenB closed this as completed May 31, 2021
@github-actions
Copy link

github-actions bot commented Jul 1, 2021

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 Jul 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants