unstale

npm / vitest-websocket-mock

vitest-websocket-mock

What changed in vitest-websocket-mock 0.6 to 0.8, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-27.

5 breaking2 behavior and defaults

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli on npm

vitest-websocket-mock 0.83 changes

Breaking changes 2

  • The matcher now returns Promise<void> instead of echoing the asserted value's type.

    0.8.0release notes

  • Vitest 5 is now required, with the peer dependency range changed from >=4 to >=5 <6; Vitest 4 is no longer supported.

    0.8.0release notes

Behavior and default changes 1

  • The matcher now returns Vitest's assertion return type instead of echoing the asserted value's type.

    0.8.0release notes

vitest-websocket-mock 0.73 changes

Breaking changes 2

  • Messages are plain text without ANSI color codes, so color detection no longer makes them differ between environments; snapshots of these messages may need updating.

    0.7.0release notes

  • The runtime dependency on @vitest/utils has been removed.

    0.7.0release notes

Behavior and default changes 1

  • Messages no longer include a manually generated Difference section; Vitest's reporter renders the diff from the matcher's actual and expected values.

    0.7.0release notes

vitest-websocket-mock 0.61 changes

Breaking changes 1

  • The peer dependency requirement is raised from >=3 to >=4, so projects using this package need Vitest 4 or later.

    0.6.0release notes