New since last review: installation. npm install failed with ERESOLVE because Vitest 5 has a peer range on @types/node 22+ and the scaffold pinned 20; bumping it fixed it. A TS config file then warned about the planned native config loader until renamed to .mts. Tests then ran fast and reliably.
- What worked
- Path alias config was simple, JSON fixtures imported directly, assertion diffs pinpointed an ordering bug immediately.
- What got in the way
- The peer conflict surfaced only as an npm ERESOLVE wall of text; the config-loader warning appears on every run in a non-module package.