Skip to content

dv 0.4.0

Latest

Choose a tag to compare

@clean99 clean99 released this 28 Oct 08:42

dv prove now supports exactly Vitest 4.1.12 alongside 3.2.x.

Added

  • dv prove supports exactly Vitest 4.1.12 alongside 3.2.x through an exact-version allowlist and pinned source fingerprints. Every other 4.x and all 5.x versions remain rejected because their body, snapshot and shutdown boundaries have not been verified. The 4.1.12 matrix covers Vite 6.4.5/7.3.7/8.3.5 on Node 20/22/24 with npm and isolated pnpm.
  • Source-checked instrumentation in phase-owned dependencies observes the original test handler after fixture resolution. Clean test/file/worker fixtures qualify; setup, teardown, detached async work, assertion-count and lifecycle errors do not. Shutdown requires empty post-close and final Vitest error collections.
  • Snapshot attribution follows 4.1.12 match results through the exact matcher-created Error, with read-only --update=none. Domain/polling snapshots, unbound custom snapshot helpers, aroundEach/aroundAll, onUnhandledError callbacks and --minWorkers are rejected on 4.1.12.
  • Effective configuration retains viteDefine keys and literal types while normalizing checkout path spans, and captures setup imports across Vite environment graphs.

Fixed

  • Deliberately tighten Vitest 3.2.x as well as 4.1.12 by rejecting functions in Vite resolver settings, including both alias customResolver forms. Previously accepted 3.2.x function resolvers now reject: identical function source cannot prove identical closed-over targets. Declarative aliases remain supported.
  • Reject direct Vitest 4.1.12 snapshot-cache reads (_snapshotData and _initialData) in forks and threads, including caught errors, so switching expected entries cannot bypass per-test snapshot binding.

Known limitations

  • Vitest 4.1.12 test bodies that directly return a resolves or rejects matcher thenable reject in both phases as unsupported test-body thenable. The observer cannot safely track that thenable as a native promise. Use await expect(p).resolves.toBe(x) inside an async test body instead of return expect(p).resolves.toBe(x); the same workaround applies to rejects.

Install

pipx install https://github.com/clean99/delivery-verifier/releases/download/v0.4.0/delivery_verifier-0.4.0-py3-none-any.whl

GitHub Action: uses: clean99/delivery-verifier@v0.4.0.