@sheremet-va let me know if theres any additional work or changes needed to move this forward. I think theres also a way to implement this as a backwards compatible change by returning thenables instead of promises. But not sure its worth it as it would make the API and implementation more complicated

Can you also prepare PRs updating vitest docs and vitest-browser-examples when this is released?

Can you also prepare PRs updating vitest docs and vitest-browser-examples when this is released?

Sure happy to do that. Should hopefully have some time free next week

👋🏼 we're quite keen to use this over at sanity is there a chance to get an experimental release in the meantime that we could test out? we use a lot of suspended components on our dashboard project.

👋🏼 we're quite keen to use this over at sanity is there a chance to get an experimental release in the meantime that we could test out? we use a lot of suspended components on our dashboard project.

This sounds good to me. We probably can't release the v2 version fully because vitest init will incorrectly produce a sync version until we make the changes there.

FYI i've just added this to an internal project & the test that was failing now works as expected. I had some issues (that weren't there before) where i needed to await MSW's start function in the beforeAll call but realistically I probably should have done that before and it "just worked" other than that, I can't see any issues at the moment.

I'll open issues for anything I do find though. Thanks again for the beta 👍🏼