Update jest to v26 along with packages related to it

[ghost]

Summary

The only problem is jest-snapshot-serializer-raw, it hasn't been updated for 2 years but tests fail without it and I couldn't find a replacement.

I see only two options here:

1. migrate the snapshot tests to another serializer or to jest default serializer.
2. fork jest-snapshot-serializer-raw

Test Plan

run the tests, tests that passed before should not fail after the upgrade, and tests that failed before should fail too

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 8c2616d:

Sandbox	Source
React	Configuration

[sizebot]

No significant bundle size changes to report.

Size changes (experimental)

Generated by 🚫 dangerJS against 8c2616d

[sizebot]

No significant bundle size changes to report.

Size changes (stable)

Generated by 🚫 dangerJS against 8c2616d

[gaearon]

Looks like there's CI failures. Ideas?

[bvaughn]

This one is a lint failure.

TypeError: jest.requireActual is not a function

This one looks to be directly caused by one of the changed files.

[ghost]

@gaearon the failure happens because fixtures was still using jest 25 in which require.requireActual must be used not jest.requireActual

[ghost]

@bvaughn the lint failure comes from updating eslint-plugin-jest

[ghost]

@gaearon Ok it seems that fixtures/dom is still using Jest 25 even after updating the jest version in all package.json files I could find. maybe because of --frozen-lock?

Anyway even after changing jest.requireActual with require.requireActual I get this error now:

TypeError: Cannot read property 'unstable_now' of undefined

This problem is probably because mocking scheduler module didn't work for some reason

[SimenB]

remove this line?

[ghost]

unfortunately that didn't fix the problem

[SimenB]

I just meant removing the todo comment

[bvaughn]

Initially a little skeptical about why bumping dependencies resulted in 25,000+ lines added to the yarn lockfiles.

[matthargett]

Initially a little skeptical about why bumping dependencies resulted in 25,000+ lines added to the yarn lockfiles.

FWIW, the jest repo's yarn.lock has increased more than 10% in the last year. it's over 680kb now. I don't think that by itself should indicate concern or a problem. Since it doesn't have a resulting bundle size impact, would timing a fully-cached 'yarn install' before and after could be enough to quell your skepticism?