Remove es5 builds

[cpojer]

Summary

We have shipped es5 builds for a very long time but they receive little usage. Their original intent was to enable people to load these packages into the browser without transformation. Nowadays most browsers support latest syntax features and app developers have bundlers available to compile and bundle npm packages. With this change, we are pushing the responsibility to bundle the affected packages themselves rather than Jest providing them out of the box.

This change will be part of Jest 26.

Test plan

The code has been terminated.

[cpojer]

Note: I left the build-es5 folder in the build clean command so that everyone rebasing past this commit will get a clean checkout without artifacts. We can remove that one in a month or so.

[SimenB]

👍

[skovhus]

Aw, the only feature I added to Jest... I should probably have added some documentation for it though. ;)

But I agree that it makes sense to remove now.

[cpojer]

@skovhus thank you for your contribution to Jest all those years ago. It was very useful when Jest was still gaining adoption. Nowadays everyone is using a bundler so they can compile these themselves.

[skovhus]

@skovhus thank you for your contribution to Jest all those years ago. It was very useful when Jest was still gaining adoption. Nowadays everyone is using a bundler so they can compile these themselves.

It is always nice when you can remove code. 👏

[jquense]

:( we were using these (sorry we've just upgraded). Compiling them is not hard, but these were also stubbing out chalk, which is a paaaaaain to do ourselves

[SimenB]

you can just copy the fake chalk we used and do module replacement.

https://github.com/facebook/jest/blob/285e4625e3f88c289ebff7b8b32ce80f6309d86d/packages/expect/src/fakeChalk.ts

You can look at the PR that added it for rollup (#4367), or this PR which removed the webpack way (which we migrated to at some point)

(Seems we haven't even removed it from our sources, which we should do.)

[github-actions]

This pull request 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.