TypeError: Cannot read property 'context' of undefined

[kentcdodds]

🐛 Bug Report

When you have a globalSetup script, this error shows up when trying to start jest with watch mode:

TypeError: Cannot read property 'context' of undefined

To Reproduce

Steps to reproduce the behavior:

git clone -b context-issue --single-branch https://github.com/kentcdodds/jest-transform-self-transform-bug.git
cd jest-transform-self-transform-bug
yarn
npx jest --watch

Expected behavior

It should start Jest in watch mode.

Link to repl or repo (highly encouraged)

I just reused the same repo from my other issue. It's on the context-issues branch here: https://github.com/kentcdodds/jest-transform-self-transform-bug/tree/context-issue

Here's the difference for the initiated: https://github.com/kentcdodds/jest-transform-self-transform-bug/compare/context-issue

Run npx envinfo --preset jest

Paste the results here:

  System:
    OS: macOS 10.14.3
    CPU: (8) x64 Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz
  Binaries:
    Node: 8.11.4 - ~/n/bin/node
    Yarn: 1.12.3 - /usr/local/bin/yarn
    npm: 6.5.0 - ~/n/bin/npm
  npmPackages:
    jest: ^24.0.0 => 24.0.0 

I pulled this up in a debugger and got this:

This code is here: https://github.com/facebook/jest/blob/2e2d2c8dedb76e71c0dfa85ed36b81d1f89e0d87/packages/jest-cli/src/runGlobalHook.js#L41-L48

The modulePath variable is the path to the globalSetup file.

Note that the tests run fine when not in watch mode.

[jeysal]

Confirmed. Probably introduced by #7562

[SimenB]

It happens since we run both setup and teardown even if there's no tests.

So it also happens if there are no tests found, and jest is run with --pass-with-no-tests

[SimenB]

See #7745. Missing a test, if anybody feels like adding one 😀

[kentcdodds]

Thanks friends 🤗

[SimenB]

@kentcdodds release is out 8a2ea1e

[kentcdodds]

Sweet!

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