Yeah, Meta will continue to use Jest internally. It still works really well for us, it's just "feature complete" for our use cases so we haven't needed to invest in it.

>Yeah, Meta will continue to use Jest internally. It still works really well for us, it's just "feature complete" for our use cases so we haven't needed to invest in it.

What's the status of Rome? Is that being looked at as a long term replacement?

Rome is a completely separate project that Meta no longer owns. You can check https://rome.tools/ for the project status.

I'm a mixed of confused and optimistic about this project.

On one hand, I would absolutely hate for someone to force me to use one tools, opinions for everything I do in a project.

On the other hand, if I just start a new job and I need to get producing, I'd rather have one big tool that just makes JavaScript work. Versus 4 different tools with a bunch of different limitations.

I have full confidence that the people working on it can deliver an incredible product. I have severe doubts that this will be sustainable as a business though, which really sucks

Wouldn't it make more sense to create the business model first ?