Regression after #12131

[satanTime]

After the fix of #12131, I'm getting an error: https://app.circleci.com/pipelines/github/ike18t/ng-mocks/2810/workflows/cad5fba3-e1c9-4e59-9d20-daf923c60c31/jobs/101406

    TypeError: Cannot read properties of undefined (reading 'bind')

      at Runtime._createJestObjectFor (node_modules/jest-runtime/build/index.js:2193:46)

is it possible that mocked isn't present in some cases?

Originally posted by @satanTime in #12131 (comment)

[satanTime]

Hi @SimenB, I found the problem.

it's because of version dependency chains.
In my repo, eventually, it ends up at @jest/environment@27.3.0 which requires jest-mock@27.3.0 which doesn't have .mocked definition.
it was requested by jest-environment-jsdom@27.3.1.

node_modules/jest-* have right version, but some packages with some internal nod_modules have elder versions and this is causes the issue.

Looks like jest-runtime cannot rely on its dependency version for jest-mock only, and, in some cases, it can receive an object which belongs to any version.

[satanTime]

The issue has been solved by npm update --depth 999 jest-environment-jsdom.

[peterlundberg]

Or as suggested here #12200 (comment) can probably get it to work with an explicit "jest-environment-jsdom": "^27.4.4" dev dependency (worked for us)

[SimenB]

https://github.com/facebook/jest/releases/tag/v27.4.6

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