Meta Is Transferring Jest to the OpenJS Foundation

This page summarizes the projects mentioned and recommended in the original post on

Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • vitest

    Next generation testing framework powered by Vite.

  • jest

    Delightful JavaScript Testing.

  • SurveyJS

    Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

    SurveyJS logo
  • tools

    Discontinued Unified developer tools for JavaScript, TypeScript, and the web

  • Rome is a completely separate project that Meta no longer owns. You can check for the project status.

  • vite

    Next generation frontend tooling. It's fast!

  • vue-router

    🚦 The official router for Vue 2

  • nextjs-vitest-example

    Vitest unit test in Next.js project

  • I'm pretty sure you can. Though I haven't tried it myself I did a search if we could integrate it into our Next.js app (Next uses Webpack internally) and found this:

  • flow-for-vscode

    Flow for Visual Studio Code

  • I wonder when they will do the same for Flow. The Flow VSCode extension is already abandoned -

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • jest-light-runner

    A Jest runner that runs tests directly in bare Node.js, without virtualizing the environment.

  • 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:

    We also mentioned it in our Jest 28 blog post:

    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.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts