When are Benchmarking and Type Testing features expected to be stabilized?

[ghost]

Similar to #8458

We’re curious about the plan to stabilize Benchmarking and Type Testing features. Currently, we can’t use these because they are marked experimental.

Also, did you consider moving the features into separate modules? Somewhat similar to how browser mode is being redesigned.

[sheremet-va]

Our next goal is working on performance features. Depending on how well it goes, benchmarking will be stable late this year, or start of next year. Typechecking will follow shortly after.

[spaceemotion]

From my experience, right now, benchmarking in Vitest feels more like an additional module that's been tacked on, but not really integrated into vitest:

1. There's only the setup() and teardown() methods on the benchmark itself, but the beforeEach etc. callbacks don't quite work. I sometimes have to decide against doing a benchmark with vitest because of concurrency issues with the current system.
2. Similarly, right now, there seems to be no way of having work be done before and after each benchmark run that shouldn't count against the benchmark time. This seems to be a limitation in tinybench, but I'd love to set up certain fixtures that are being mutated during the run - currently, their creation time is included.
3. I am frequently running into clean up issues with promises not being flushed after each run, out of memory errors, etc. When using regular tests these cases seem to be handled better? Doing any larger benchmarks has been very risky so far, so we've mostly been doing micro-benchmarking of certain features/converters/etc.

[sheremet-va]

#7850

[spaceemotion]

thanks! will copy my experience over to the other discussion.