Heath C

@fivethreeo Also, I'm wondering if you upgraded to `jest@27` whether this is still a problem? I made a [branch](https://github.com/heath-freenome/razzle-4-tests-fail/tree/razzle-4-jest-27-tests) where I explicitly call jest@27 to run my tests on top...

I don't know what to say about that. You can just pay attention to the `master` and `razzle-4-tests-break` branches of the repo I linked above if you are willing to...

I'm not entirely sure 26 => 27 would fix it anyway... I wonder if there is anything that jumps out at you related to the losing of the `env.tests.plugin` set...

Enjoy your vacation

Ok, so I'm wondering if it has something with the `razzle-babel-preset` changes in 4? I set the following in the preset config and the problems in the tests went away,...

Whoops, I missed this since I gave up and switched back to calling jest directly with a `jest.config.json`... Did you mean: ``` "env": { "test": { "presets": [ [ "razzle/babel",...

Bump... Jest updated to 27.x which dependabot would have let you know about

> Npm 7? Because razzle does not support that yet. Need to split razzle into a wp4 and wp5 version first since npm 7 has stricter deps. No, `6.14.11` I...

Ah... Yep it is the latter... I probably can remove my one-off customizations I originally added to get webpack 5 to work...

When you get webpack 5 working, can you make sure that all of the plugins are updated? especially mini-css-plugin which on 4.x is locked on one that is two versions...