@jest/globals doesn't seem to work with jest.mock

[Vinnl]

🐛 Bug Report

When importing jest from @jest/globals, and running jest.mock, I get:

  ● Test suite failed to run

    TypeError: Cannot read property 'jest' of undefined

      2 | import { jest, it, expect } from "@jest/globals";
      3 | // import { it, expect } from "@jest/globals";
    > 4 | jest.mock('./mocked.ts');
        | ^

That's what I get in the minimal reproduction repo. In my regular code, I instead get this error:

ReferenceError: Cannot access 'globals_1' before initialization

To Reproduce

Steps to reproduce the behavior:

1. git clone git@github.com:Vinnl/ts-jest-repro.git --branch globals-mock
   (Note that this is not on the master branch.)
2. npm install
3. npm test

This is a repository with Jest and ts-jest setup. The problematic code is:

// COMMENT OUT THE (jest) IMPORT TO MAKE THIS WORK AGAIN
import { jest, it, expect } from "@jest/globals";
// import { it, expect } from "@jest/globals";
jest.mock('./mocked.ts');

import { add } from './add';

it('should properly add', () => {
	expect(add(1, 2)).toBe(3);
});

Expected behavior

The test to run successfully.

Link to repl or repo (highly encouraged)

git clone git@github.com:Vinnl/ts-jest-repro.git --branch globals-mock

envinfo

$  npx envinfo --preset jest 
npx: installed 1 in 0.889s

  System:
    OS: Linux 5.4 Ubuntu 20.04 LTS (Focal Fossa)
    CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
  Binaries:
    Node: 12.16.1 - ~/.nvm/versions/node/v12.16.1/bin/node
    Yarn: 1.22.4 - /usr/bin/yarn
    npm: 6.13.4 - ~/.nvm/versions/node/v12.16.1/bin/npm
  npmPackages:
    jest: ^26.0.1 => 26.0.1 

[ahnpnl]

Possibly related to the fact that ts-jest doesn’t have the hoisting implementation yet like Babel-jest, see kulshekhar/ts-jest#1593

[SimenB]

Yep, this will only work properly with babel-plugin-jest-hoist (included in babel-jest config). If you use another transformer, that will need to support it

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