[Bug]: Cannot assign to read only property 'performance' of object '[object global]' on Node 20

[antonio-ivanovski]

Version

29.7.0

Steps to reproduce

1. Setup Node 20
2. Create test
3. Use jest.useFakeTimers
4. Run the test

Expected behavior

Jest runs the test and mock the timers and I can set my own time

Actual behavior

Test fails with

TypeError: Cannot assign to read only property 'performance' of object '[object global]'
jest.useFakeTimers().setSystemTime(new Date('2022-06-06'));
    ^

Additional context

On Node 18 is OK, upgrading to Node 20 causes issues both locally and on CI

Related to: facebook/react-native#35701

Environment

System:
    OS: macOS 14.0
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Binaries:
    Node: 20.10.0 - /private/var/folders/_3/ggprgl2s3dg02ll3pgymf2280000gn/T/xfs-bffabcd0/node
    Yarn: 4.0.1 - /private/var/folders/_3/ggprgl2s3dg02ll3pgymf2280000gn/T/xfs-bffabcd0/yarn
    npm: 10.2.3 - ~/.nvm/versions/node/v20.10.0/bin/npm
  npmPackages:
    jest: ^29.7.0 => 29.7.0

[github-actions]

As noted in the Bug Report template, all bug reports requires a minimal reproduction. Please open up a new issue providing one. Read more at https://stackoverflow.com/help/minimal-reproducible-example.

[satazor]

I'm having the same issue and I've found this related issue on Node.js: nodejs/node#51048

It seems latest 18 have this issue as well.

[SimenB]

That's a link to this very issue.

But again, please put together a reproduction. "+1" doesn't really help us

[satazor]

Sorry my mistake. I have updated the link.

[satazor]

I have created a reproducible repo here: https://github.com/satazor/jest-issue-14741. The issue only happens in Jest v28 and not in the latest v29.

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

[SimenB]

I have created a reproducible repo here: https://github.com/satazor/jest-issue-14741. The issue only happens in Jest v28 and not in the latest v29.

v28 is unsupported. However, you should be able to use v29 test env in v28 to work around the issue if you're unable to upgrade.