tuanbass
commented
1 year ago It's caused by an open issue in node:
https://github.com/nodejs/node/issues/35889 actually the problem in V8 js engine https://bugs.chromium.org/p/chromium/issues/detail?id=1238312
Cause: when running test suites, jest try to isolate the running environment for each suite. to do so, it uses VM from nodejs (actually Chrome V8 js engine). However, the VM module is experiment and contains a crash bug (which openned for ~ 2 years). See detail in the above link.
Proposal: Use another Jest runner just does not use VM module. Impact: Suite isolation must be cared by the dev
Something not supported by jest-light-runner
- import/require mocks. You can use a custom mocking library such as esmock or proxyquire.
- On-the-fly compilation (for example, with Babel or TypeScript). You can use a Node.js module loader, such as ts-node/esm.
- Tests isolation. Jest runs every test file in its own global environment, meaning that modification to built-ins done in one test file don't affect other test files. This is not supported, but you can use the Node.js option --frozen-intrinsics to prevent such modifications.
- import.meta.jest. You can use the jest global instead.
When running test require VM module (knex for sample), sometime jest is crashed.