Simen Bekkhus

Landed a bit of this in #9545, all the things `yarn install` complained about and the ones I noticed when running tests. Still a bunch of failures, will need to...

Reviving this now that we've landed Yarn v2 with node-modules linker on master. I'll try to get PnP working here. As before, any changes not strictly related to PnP stuff...

Can remove the packageExtensions as yarn does it automatically: https://github.com/yarnpkg/berry/pull/1847/files

@merceyz hey, happy new year! 😀 Would you be able to take a look at the error with lint and typescript? - https://github.com/facebook/jest/actions/runs/3818199835/jobs/6494956216 - there's a weird require: https://github.com/taskworld/eslint-plugin-local/blob/master/index.js#L1 -...

Thanks for taking a look! --- The `WebAssembly` issue seems to be an old one: https://github.com/microsoft/TypeScript-DOM-lib-generator/issues/826

Sorry about the regression but >sorry can't share our codebase means we can do absolutely nothing. This is the first I've heard of performance regressing, everywhere else I've heard from...

Your configuration, especially `transforms` and setup files are probably relevant as well >what do you recommend with regards to clearing cache before running tests in CI I personally think it's...

Interesting! We've updated Istanbul to v3, maybe something in there has regressed. We've added support for v8 code coverage, so I might also have messed up the refactoring when doing...

I'm unable to reproduce this - the repos I test have about the same performance with `--coverage` between v24 and v25. Would somebody be able to put together a repository...

Any JS traces at all? Would be interesting to see where it died. >I also noticed Jest 25 handles the collectCoverageFrom differently as it seems to collect coverage from files...