`yarn check` prints out two warnings when installing the latest Jest 24.4.0 packages

[kaiyoma]

🐛 Bug Report

yarn check prints out two warnings when installing the latest Jest 24.4.0 packages.

To Reproduce

Install the latest Jest 24.4.0 packages. Observe these warnings:

warning "jest > jest-cli > @jest/core > jest-resolve-dependencies@24.4.0" has unmet peer dependency "jest-resolve@^24.1.0".
warning "jest > jest-cli > jest-config > jest-resolve@24.4.0" has unmet peer dependency "jest-haste-map@^24.0.0".

Expected behavior

No warnings.

Run npx envinfo --preset jest

Paste the results here:

$ npx envinfo --preset jest
Error: EPERM: operation not permitted, mkdir <redacted>
TypeError: Cannot read property 'get' of undefined

[danvc]

Having the same issue over here.
npx envinfo --preset jest:
npx: installed 1 in 2.321s

System:
OS: Linux 4.9 CentOS Linux 7 (Core)
CPU: (2) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Binaries:
Node: 8.15.0 - /usr/bin/node
Yarn: 1.13.0 - /usr/bin/yarn
npm: 6.4.1 - /usr/bin/npm
npmPackages:
jest: 24.5.0 => 24.5.0

[angeloocana]

same here!
We are using Windows 10

[kaiyoma]

Also seeing this on our Linux build machines.

npx: installed 1 in 2.049s

  System:
    OS: Linux 4.14 CentOS Linux 7 (Core)
    CPU: (48) x64 Intel(R) Xeon(R) Gold 5118 CPU @ 2.30GHz
  Binaries:
    Node: 10.15.0 - /usr/local/bin/node
    Yarn: 1.13.0 - /usr/local/bin/yarn
    npm: 6.4.1 - /usr/local/bin/npm

[pndewit]

Same for me using macOS with Jest 24.5.0.

System:
  OS: macOS Mojave v10.14.3
  CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz

Binaries:
  Node: 10.15.1 - ~/.nvm/versions/node/v10.15.1/bin/node
  Yarn: 1.13.0 - ~/.nvm/versions/node/v10.15.1/bin/yarn
  npm: 6.4.1 - ~/.nvm/versions/node/v10.15.1/bin/npm

  npmPackages:
    jest: ^24.5.0 => 24.5.0

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