Jest 12.0.2.

Summary: Closes jestjs#952

Differential Revision: D3234626

fb-gh-sync-id: e0526f037a4a517e82e3afcb6659a301d3d14918
fbshipit-source-id: e0526f037a4a517e82e3afcb6659a301d3d14918

v10.0.0

0.9.0.

Summary:yay!
Closes jestjs#769

Differential Revision: D3015097

fb-gh-sync-id: be6aaf09a2fca4096ea6fcc49ebc6f748559a4ea
shipit-source-id: be6aaf09a2fca4096ea6fcc49ebc6f748559a4ea

added back aggragate collector

Reviewed By: cpojer

Differential Revision: D2758014

fb-gh-sync-id: 681b5a0b75d3252a7dffacfb68d0885c7148b6e4

Simplify module execution.

Summary:
Pulled out from jestjs#599.
Closes jestjs#636

Reviewed By: vjeux

Differential Revision: D2731701

fb-gh-sync-id: 23fbcc618dc9e0cfb79fb96a8d02302b3276466a

Bump version; fix npm test.

Summary: Closes jestjs#619

Reviewed By: svcscm

Differential Revision: D2671339

fb-gh-sync-id: 77fb47278a74024aaccd57690cfb1db16280d21f

Bump version.

Summary: Closes jestjs#592

Reviewed By: svcscm

Differential Revision: D2614888

fb-gh-sync-id: 573a5e0cf25616bcaaf611128545550194dd07cb

Fix memory leak around `global.process`

Summary: This memory leak was discovered in jestjs#584 and has always been present in jest. It likely affects the runtime performance of jest on low-memory machines *a lot* and we don't notice it much on devservers. I will tag and release 0.7.0 with this fix (because 0.7.0 also removes a bunch of APIs, see the changelog, it cannot be a patch release).

Two samples from before and after:

* P20276376 (150 mb vs 47 mb on 34 Relay tests)
* P20276601 (54 mb vs 38 mb flat on the functional tests)

I also added a way to pretty print the output (see the second paste). By adding `--logHeapUsage` to jest it adds these statistics after every test run. When node's global `gc` function is exposed, it calls it beforehand to make sure we are logging accurate data. I am going to think about whether it makes sense to expose this more easily (adding `--runInBand` etc. is slightly confusing) if I am confident it isn't bad for performance. On automated test runs you might want to log this and be able to log the final memory usage to whatever logging system you use to be able to track memory usage of test runs (and applications) over time.

Note: It is time we rewrite jest's configs *completely*. I have plans for this and it is a discussion for a separate diff. For now I have to copy-pasta some code to make everything work in the internal and external runners and tack on the argv data to the config objects.

public

Reviewed By: DmitrySoshnikov

Differential Revision: D2608363

fb-gh-sync-id: ab3bda143c22ef06e2e1b32a4c92d8ad0a2151cb