Rishi Sharma

> > @phawxby nothing new since the last activity, feel free to fix: [#12205 (comment)](https://github.com/facebook/jest/pull/12205#discussion_r815307518) > > As you noted in the thread above, the `importModuleDynamically` issue could be a...

We're also experiencing this issue. Node **16.11+** and Jest v27 consumes significantly more memory. Node **16.10** and Jest v27 seems OK.

@blimmer nothing in particular is notable about our codebase. It's not a small codebase, but not very big either. Prior to 16.11, there were known memory leaks when running test...

For those interested, I'm inviting you to join us in a live discussion about this problem. We'll be online over Zoom for two hours on Friday at 8am ET to...

@PAkerstrand some notes: - The performance regression is likely contained to `vm.Script` and so running Node 16.11+ in production should not experience the performance regression. - The memory leak appears...

> What worked for me was combining the 2 node flags: `--no-compilation-cache` and `--expose-gc`. Using [this example above](https://github.com/facebook/jest/issues/11956#issuecomment-984439195) I've managed to run `node --no-compilation-cache --expose-gc ./node_modules/jest/bin/jest.js --runInBand --logHeapUsage` and got...

https://swc.rs/docs/usage/jest has been a good drop-in replacement for us.

Fwiw, Node 16 has both Script and compileFunction performing similarly: ```bash rishi vm-script-vs-compile-function % nvm use 14 Now using node v14.18.2 (npm v6.14.15) rishi vm-script-vs-compile-function % node index.js Running with...