TypeError: environment.dispose is not a function

[ShMcK]

What is the current behavior?

All tests files fail with the following error:

 TypeError: environment.dispose is not a function

      at Promise.resolve.then (../../../../../usr/local/lib/node_modules/jest/node_modules/jest-runner/build/run_test.js:116:17)
          at <anonymous>
      at process._tickCallback (internal/process/next_tick.js:188:7)

Tests were running yesterday.

Removing node_modules & reinstalling produced no difference.

Dependencies:
"jest": "^22.1.4",

with presets:
"jest-expo": "^25.0.0"

[ShMcK]

Fix: installed jest globally rather than running from local npm script.

[spudly]

Just ran into the same issue. Upgraded jest and the error went away.

[etcetera8]

npm install jest-cli fixed this one for me

[SimenB]

Should be fixed in newer versions of jest (22.2.0+). See #5294, #5304 and #5353

[wilhelmklopp]

Updating Jest didn't fix this for me.

npm install jest-cli fixed this one for me

But this did 🙌

[AndreiCalazans]

I also had to uninstall jest first,
npm uninstall jest
then do
npm install jest-cli

I'm using create-react-app.

[matej-prokop]

If you are using create-react-app then TypeError: environment.dispose is not a function is very probably caused by clash of jest-environment-node versions. Try to run:

npm ls jest-environment-node

to see which of your dependencies is causing it.

In my case it was caused by upgrade of lint-staged to v 7.0.0. (lint-staged/lint-staged#414)

[jonathan-stone]

I got this using create-react-app after installing jest-enzyme.
Fixed by updating jest with yarn upgrade jest.

[gaearon]

It is not supported to "upgrade Jest" inside a CRA-managed project. If you have both react-scripts and jest in your package.json things will go badly wrong in the future.

[gaearon]

I filed a new issue for this problem. I think it's a Jest bug (that hasn't been fixed yet). #5913

[gaearon]

@AndreiCalazans @jonathan-stone

Please, could you report such issues to CRA in the future? We had no idea people were doing workarounds like installing Jest into a CRA project (which is entirely unsupported and will break your projects later). If something doesn't work in CRA out of the box, it's CRA's fault, and we want to be aware of it so we can fix it for our users. Thanks!