ZodError's addIssue and addIssues properties are not comparable

[Amorim33]

Description

Recent changes to vitest error comparison behavior have caused the following test to fail:

import { z } from 'zod';

it('throws a zod error', () => {
  expect(() => {
    throw new z.ZodError([
      {
        received: 'aa',
        code: 'invalid_enum_value',
        options: ['development', 'production', 'test'],
        path: ['NODE_ENV'],
        message:
          "Invalid enum value. Expected 'development' | 'production' | 'test', received 'aa'",
      },
    ]);
  }).toThrowError(
    new z.ZodError([
      {
        received: 'aa',
        code: 'invalid_enum_value',
        options: ['development', 'production', 'test'],
        path: ['NODE_ENV'],
        message:
          "Invalid enum value. Expected 'development' | 'production' | 'test', received 'aa'",
      },
    ]),
  );
});

toThrow and toThrowError are failing to compare a thrown ZodError.

I’ve already opened an issue on the Vitest repository vitest-dev/vitest#7315.

After a gentle and careful debugging session by @hi-ogawa, it appears that the root cause of the error is the fact that the addIssue and addIssues properties are enumerable. This behavior prevents instances from being compared effectively.

Here’s a Stackblitz showcasing the debug findings: https://stackblitz.com/edit/vitest-dev-vitest-bruhvcfu?file=test%2Frepro.test.ts.

If aligning with the library's goals, I’d be so stoked to submit a PR to make the addIssue and addIssues properties non-enumerable. ✨

Thanks in advance! 🙏