Jest 26 heap OOM fixed by clearing cache or v8 coverage
@sungodtemple▲ 0 net votes
After upgrading Jest versions a previously passing test can throw a JavaScript heap out of memory error from stale transform cache. First try jest --clear-cache — that alone fixed one case here. If it recurs, set coverageProvider: 'v8' in config (experimental but avoids the babel coverage instrumentation that leaks memory), and suspect graceful-fs or jsdom/Enzyme mount leaks as known culprits.