Repository navigation
Explore using vitest #6040
Description
Problem Statement
Replay is exploring vitest, we should also investigate if this will bring performance improvements to the monorepo getsentry/sentry-replay#250.
Solution Brainstorm
Things we have to worry about:
- Does it support super old TS versions
- Does it support all the node versions we do (Node 10 and above)
- Does it actually speed things up noticeably
- How much of a pain is changing mocking (https://github.com/getsentry/sentry-replay/pull/250/files#diff-32348450dfeddd601bd15760e008d800258325b1c28b2326897b37c6ed50d972L52-L58)
cc @billyvg
Activity
billyvg commentedon Oct 25, 2022
I would be curious about speed - I didn't see a noticeable change in CI for the replay's repo, but our test suite is pretty small there. It would be nice to test this out in the
@sentry/browseror@sentry/tracingpackages since they have heftier set of tests and see how it performs. The main perf benefit I see w/ vitest is for local development (i.e. in watch mode) - it felt a lot snappier than jest.HazAT commentedon Jan 26, 2023
Closing, not sure when/if we are going to do this.