Skip to content

v0.8.1

Latest

Choose a tag to compare

@mareszhar mareszhar released this 07 Oct 17:46

Summary

Vanity's testing kit now accepts Selenita 0.4 while preserving 0.3 compatibility. This patch also clarifies how to restart the development server when updating dependencies.

Fixed

  • Selenita compatibility. The testing kit's optional peer range now includes Selenita 0.4 (>=0.3.0 <0.5.0). The recommended setup uses 0.4.1, with observations independent of assertion order and markers that work across separate installs of the same version.

Documentation

  • Dependency updates. Stop the development server before updating Vanity or its build host, then start it after installation completes. Reloading the browser does not restart loaded compiler code. The guide also explains how to investigate compilation errors that persist after restarting.
  • Editor-DX tests. The testing guide explains independent observations and marker compatibility. Vanity's auto-import tests now recheck Selenita's native completion actions directly.

Upgrading

Existing applications need no migration. Selenita remains optional, and TypeScript and Vitest requirements are unchanged.

For editor-DX tests, the recommended Selenita version is:

pnpm add -D @mszr/selenita@^0.4.1

If upgrading Selenita from 0.3:

  • Replace its CodeFix type imports with CodeAction.
  • Keep Selenita copies that exchange fixture markers on the same version.
  • Review any changed editor assertions: observations no longer depend on which assertion ran first. Diagnostics-first warming cannot establish what a user sees while typing.