# What changed in vitest-websocket-mock

> 7 changes in vitest-websocket-mock 0.6 to 0.8 from its official release notes, upgrade guides and advisories: 5 breaking. Each one cited. Sources checked 2026-10-27. HTML: https://unstale.sh/npm/vitest-websocket-mock/

To see which of these apply to a repository, run `npx @unstale/cli init` in it.

## vitest-websocket-mock 0.8

### Breaking changes

- The matcher now returns Promise<void> instead of echoing the asserted value's type. (0.8.0) — [release notes](https://github.com/akiomik/vitest-websocket-mock/releases/tag/v0.8.0)
- Vitest 5 is now required, with the peer dependency range changed from >=4 to >=5 <6; Vitest 4 is no longer supported. (0.8.0) — [release notes](https://github.com/akiomik/vitest-websocket-mock/releases/tag/v0.8.0)

### Behavior and default changes

- The matcher now returns Vitest's assertion return type instead of echoing the asserted value's type. (0.8.0) — [release notes](https://github.com/akiomik/vitest-websocket-mock/releases/tag/v0.8.0)

## vitest-websocket-mock 0.7

### Breaking changes

- 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.0) — [release notes](https://github.com/akiomik/vitest-websocket-mock/releases/tag/v0.7.0)
- The runtime dependency on @vitest/utils has been removed. (0.7.0) — [release notes](https://github.com/akiomik/vitest-websocket-mock/releases/tag/v0.7.0)

### Behavior and default changes

- 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.0) — [release notes](https://github.com/akiomik/vitest-websocket-mock/releases/tag/v0.7.0)

## vitest-websocket-mock 0.6

### Breaking changes

- The peer dependency requirement is raised from >=3 to >=4, so projects using this package need Vitest 4 or later. (0.6.0) — [release notes](https://github.com/akiomik/vitest-websocket-mock/releases/tag/v0.6.0)