flow-for-vscode VS jest-light-runner

I wonder when they will do the same for Flow. The Flow VSCode extension is already abandoned - https://github.com/flow/flow-for-vscode

I ran into some compatibility issues with Flow and VS Code. If you run into issues make sure you follow the instructions here. I also had to change the version in .flowconfig to >=0.107.0.

Hi! Christoph from Jest here. Your feedback is great, and 100% valid. Jest was built a long time ago when ES modules did not exist, and we are still carrying some of that legacy baggage around.

The good news is that we have never been shy about making breaking changes and we are working on cleaning the house and making many legacy components optional, all while bringing the existing community with us.

As for mocking, you don’t have to rely on Jest’s inbuilt mocking libraries and you can use the ones you like better.

If you care more about raw performance and ES module support and less about isolation, check out the jest-light-runner: https://github.com/nicolo-ribaudo/jest-light-runner

We also mentioned it in our Jest 28 blog post: https://jestjs.io/blog/2022/04/25/jest-28

I’m wondering if it’s time to consider taking a big step and making this runner the default, and give people the optionality of isolation. However, in my past experience at large companies (both first-hand and second-hand experience), the lack of isolation in tests led to major reliability problems with testing infrastructure. I’m still feeling like it’s the better default today, but maybe we should have a serious discussion about Jest’s next set of defaults.