Simen Bekkhus
Simen Bekkhus
We originally planned to write codemods for Jest to handle API renames, but nobody had the energy to make it happen, so we never did 😀 The ESLint plugin can...
Yep, but that requires time and effort to write, of which volunteers often have little 🙂
maybe we could somehow pass in the config so you could delegate to other serializers first, then do your diff?
I have not touched the integration in months. It's been active since maybe a couple of days since you made it available.
It happened again at the beginning of June this year for me: https://github.com/SimenB/available-cpu/issues?utf8=%E2%9C%93&q=is%3Aissue 
RN should probably have its own test environment that's neither "node" or "browser". If that's actually JSC/Hermes or not would then be up to the env. It'd need to support...
> It would be good if Jest had support for customizing the name of `main` fields like Metro does. It does - just provide a custom resolver. There's an example...
It's currently unsupported, but I'd happily merge a PR to jest adding support for passing options to `coverageReporters` similar to how you can pass options to `reporters` today 👍 Regarding...
Nope, that's not supported. You can use `nyc` on the coverage reports that are output in the `coverage` directory, though (or custom `coverageDirectory` if you've set that)
Jest's reporting is async, so it would not be a big issue for us to migrate to an async API 👍 Instrumentation would need to stay sync (that's a Babel...