feat: spy.mockRevert

[Lordfirespeed]

Description

Adds a new method mockRevert to spies. It's in the same vein as mockClear, mockReset, mockRestore - it is most similar to mockRestore, with the key difference being that it does not 'un-spy' mocks created with vi.spyOn().

See #6308 for discussion.

PR Checklist

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci. (I am waiting for playwright to install)

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[netlify]

✅ Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	95a1d1c
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/66c7bf6c885d9c000843e32d
😎 Deploy Preview	https://deploy-preview-6378--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Lordfirespeed]

Hey, I'd appreciate some input on the CI failing - node-20, macos-14 was passing before my rebase onto main 🤔

[sheremet-va]

Hey, I'd appreciate some input on the CI failing - node-20, macos-14 was passing before my rebase onto main 🤔

It's just flaky, don't worry

[sheremet-va]

The team thinks it's better to restore the implementation in mockRevert instead of resetting it to a () => {} without adding a new method.

[Lordfirespeed]

mockRevert is the function this PR adds - do you mean mockReset ?

Wouldn't that be a breaking change with respect to the Jest compatibility layer?

I am imagining like:

import { expect, it, vi } from "vitest"

// this test passes with jest
// it would not pass in vitest with the proposed changes to `mockReset`
it("should reset", () => {
  const value = 0
  const fn = vi.fn(() => {
    value++
  })
  fn()
  expect(value).toBe(1)
  fn.mockReset()
  fn()
  expect(value).toBe(1)
})

Please let me know if I have misunderstood anything ❤️

Sorry, I am happy to help, I just want to make sure the discussion was rigorous before proceeding 😅

[sheremet-va]

mockRevert is the function this PR adds - do you mean mockReset ?

Wouldn't that be a breaking change with respect to the Jest compatibility layer?

Yes and yes

[Lordfirespeed]

Alright - I think I will close this for now, then, and open a new PR for that