@williamthorsen/nmr 0.55.0 → 1.0.0

package/dist/esm/vitest-source-resolution.js

@@ -1,10 +1,9 @@
 import { existsSync, readFileSync, realpathSync, statSync } from 'node:fs';
 import { isBuiltin } from 'node:module';
 import path from 'node:path';
-import { UserError } from '@williamthorsen/nmr-core';
+import { isRecord, UserError } from '@williamthorsen/nmr-core';
 import { findDirectoryChainMatch } from '@williamthorsen/toolbelt.filesystem';
 import { parsePackageJson } from "./helpers/package-json.js";
-import { isObject } from "./helpers/type-guards.js";
 const SHARED_CONDITIONS = ['module', 'import', 'development', 'default'];
 const CLIENT_CONDITION = 'browser';
 const SERVER_CONDITION = 'node';
@@ -32,7 +31,7 @@ export function resolveSourceTarget(specifier, importer, context) {
     if (packageDir === undefined || isInsideNodeModules(packageDir))
         return undefined;
     const manifest = readManifest(packageDir, context.manifests);
-    if (!isObject(manifest))
+    if (!isRecord(manifest))
         return undefined;
     const matchedSubpath = matchSubpath(manifest['exports'], parsedSpecifier.subpath);
     if (!matchedSubpath)
@@ -72,7 +71,7 @@ function findSelfReferenceDir(name, fromDir) {
         const file = path.join(dir, 'package.json');
         if (existsSync(file)) {
             const parsedManifest = parsePackageJson(readFileSync(file, 'utf8'), file);
-            return isObject(parsedManifest) && parsedManifest['name'] === name && parsedManifest['exports'] !== undefined
+            return isRecord(parsedManifest) && parsedManifest['name'] === name && parsedManifest['exports'] !== undefined
                 ? dir
                 : undefined;
         }
@@ -122,7 +121,7 @@ function isInsideNodeModules(dir) {
 function matchSubpath(exportsValue, subpath) {
     if (exportsValue === undefined)
         return undefined;
-    if (!isObject(exportsValue) || Object.keys(exportsValue).every((key) => !key.startsWith('.'))) {
+    if (!isRecord(exportsValue) || Object.keys(exportsValue).every((key) => !key.startsWith('.'))) {
         return subpath === '.' ? { value: exportsValue } : undefined;
     }
     const exactValue = exportsValue[subpath];
@@ -181,7 +180,7 @@ function selectTarget(value, conditions) {
         }
         return undefined;
     }
-    if (!isObject(value))
+    if (!isRecord(value))
         return undefined;
     const source = value[SOURCE_CONDITION];
     if (source !== undefined) {

package/dist/esm/vitest-temp-isolation.d.ts

@@ -0,0 +1,2 @@
+/** Creates this run's temp directory, points `TMPDIR` at it, and returns the teardown that removes it. */
+export declare function setup(): () => void;

package/dist/esm/vitest-temp-isolation.js

@@ -0,0 +1,44 @@
+import fs from 'node:fs';
+import os from 'node:os';
+import path from 'node:path';
+import { hasErrnoCode } from '@williamthorsen/nmr-core';
+const RUN_DIR_PREFIX = 'nmr-vitest-';
+const RUN_DIR_PATTERN = /^nmr-vitest-([1-9]\d*)-./;
+export function setup() {
+    const baseDir = os.tmpdir();
+    removeOrphanedRunDirs(baseDir);
+    const runDir = fs.mkdtempSync(path.join(baseDir, `${RUN_DIR_PREFIX}${process.pid}-`));
+    const previousTmpdir = process.env['TMPDIR'];
+    process.env['TMPDIR'] = runDir;
+    return function teardown() {
+        if (previousTmpdir === undefined) {
+            delete process.env['TMPDIR'];
+        }
+        else {
+            process.env['TMPDIR'] = previousTmpdir;
+        }
+        fs.rmSync(runDir, { force: true, maxRetries: 5, recursive: true });
+    };
+}
+function isProcessGone(pid) {
+    try {
+        process.kill(pid, 0);
+        return false;
+    }
+    catch (error) {
+        return hasErrnoCode(error, 'ESRCH');
+    }
+}
+function removeOrphanedRunDirs(baseDir) {
+    const entries = fs.readdirSync(baseDir, { withFileTypes: true });
+    for (const entry of entries) {
+        const pidText = RUN_DIR_PATTERN.exec(entry.name)?.[1];
+        if (!entry.isDirectory() || pidText === undefined || !isProcessGone(Number(pidText)))
+            continue;
+        try {
+            fs.rmSync(path.join(baseDir, entry.name), { force: true, recursive: true });
+        }
+        catch {
+        }
+    }
+}

package/dist/esm/vitest.d.ts

@@ -44,6 +44,15 @@ export interface VitestConfigOptions {
      * Turn it off only when a suite is meant to read the developer's own git configuration.
      */
     shouldIsolateGit?: boolean;
+    /**
+     * Loads nmr's temp-isolation global setup into the root config. Defaults to `true`. The setup gives the run a
+     * directory of its own under the temp directory in effect at startup, points `TMPDIR` at it for every worker and
+     * every process that a test spawns, and removes it when the run ends, along with any that an interrupted run left
+     * behind. Vitest runs a project's own `globalSetup` before the root's, so one that a layer adds through `project`
+     * runs outside the run directory. Turn the isolation off only when a suite must leave files in the ambient temp
+     * directory after the run.
+     */
+    shouldIsolateTempDir?: boolean;
     /**
      * Resolves a package whose files are outside every `node_modules` through its `source` export condition, so a
      * suite runs without a prior build. Defaults to `true`. A package that does not declare a `source` condition is

package/dist/esm/vitest.js

@@ -1,9 +1,9 @@
 import os from 'node:os';
 import path from 'node:path';
 import { fileURLToPath } from 'node:url';
+import { isRecord } from '@williamthorsen/nmr-core';
 import { defaultExclude, mergeConfig } from 'vitest/config';
 import { listGitIgnoredPaths } from "./git-ignored-paths.js";
-import { isObject } from "./helpers/type-guards.js";
 import { ALL_TEST_PATTERNS, buildTierPatterns, TEST_COLLECTION_EXCLUDE, TIER_NAMES } from "./tiers.js";
 import { deriveDefaultMaxWorkers, readMaxWorkersFlag } from "./vitest-max-workers.js";
 import { createSourceResolutionPlugin } from "./vitest-source-resolution.js";
@@ -12,7 +12,8 @@ import { toWorkspacePackageGlobs } from "./workspace-globs.js";
 const [RESIDUAL_TIER, ...NAMED_TIERS] = TIER_NAMES;
 const TIERED_PATTERNS = NAMED_TIERS.flatMap(buildTierPatterns);
 const TIER_TIMEOUT_MS = 30_000;
-const GIT_ISOLATION_SETUP_FILE = resolveGitIsolationSetupFile();
+const GIT_ISOLATION_SETUP_FILE = resolveSiblingModule('vitest-git-isolation');
+const TEMP_ISOLATION_SETUP_FILE = resolveSiblingModule('vitest-temp-isolation');
 const CLIENT_CONDITIONS = ['module', 'browser', 'development|production'];
 const SERVER_CONDITIONS = ['module', 'node', 'development|production'];
 const COVERAGE_EXCLUDE = ['**/__{fixtures,mocks,tests}__/**', '**/index.ts', '**/*.d.ts'];
@@ -22,6 +23,7 @@ const RECOGNIZED_OPTIONS = {
     project: true,
     root: true,
     shouldIsolateGit: true,
+    shouldIsolateTempDir: true,
     shouldResolveFromSource: true,
     testCollectionExclude: true,
     tiers: true,
@@ -44,7 +46,7 @@ export function defineVitestConfig(...layers) {
 }
 export function defineRootVitestConfig(...layers) {
     const lastLayer = layers.at(-1);
-    const monorepoRoot = isObject(lastLayer) ? lastLayer['monorepoRoot'] : undefined;
+    const monorepoRoot = isRecord(lastLayer) ? lastLayer['monorepoRoot'] : undefined;
     if (typeof monorepoRoot !== 'string' || !path.isAbsolute(monorepoRoot)) {
         throw new TypeError(MISSING_MONOREPO_ROOT);
     }
@@ -74,6 +76,7 @@ function buildConfig(declaredLayers, { coverageInclude, ignoredPathsRoot, projec
                 include: coverageInclude,
                 provider: 'v8',
             },
+            ...(resolveFlag(layers, 'shouldIsolateTempDir', true) && { globalSetup: [TEMP_ISOLATION_SETUP_FILE] }),
             passWithNoTests: true,
             projects: buildProjects(layers, projectExclude, projectRoot, ignoredPathsRoot),
             silent: 'passed-only',
@@ -189,7 +192,7 @@ function resolveFlag(layers, name, isOnByDefault) {
     }
     return resolvedFlag;
 }
-function resolveGitIsolationSetupFile() {
+function resolveSiblingModule(basename) {
     const thisFile = fileURLToPath(import.meta.url);
-    return path.join(path.dirname(thisFile), `vitest-git-isolation${path.extname(thisFile)}`);
+    return path.join(path.dirname(thisFile), `${basename}${path.extname(thisFile)}`);
 }

package/docs/reporting.md

@@ -64,13 +64,13 @@ Because the format is nmr's own reporting, and nmr does not tell the commands th
 
 ## Reserved environment variables
 
-`NMR_COMMAND_VERBOSITY` is nmr's own, and sets how loudly a run reports the output of the commands that it runs. Its values are `full` and `quiet`; nmr reports any other non-empty value and exits 1, rather than falling back to a mode that nobody chose, and an empty value reads as unset. Each process in a chain suppresses the output of the command that it runs rather than of everything below it, so the failing command's output still prints on a failure. It governs those commands' output alone: nmr's [verdicts](#what-nmr-reports) print in every verbosity, and the override notice is the one message that a quiet run withholds.
+`NMR_COMMAND_VERBOSITY` is nmr's own, and sets how loudly a run reports the output of the commands that it runs. Its values are `full` and `quiet`; nmr reports any other non-empty value as a usage error and exits 2, rather than falling back to a mode that nobody chose, and an empty value reads as unset. Each process in a chain suppresses the output of the command that it runs rather than of everything below it, so the failing command's output still prints on a failure. It governs those commands' output alone: nmr's [verdicts](#what-nmr-reports) print in every verbosity, and the override notice is the one message that a quiet run withholds.
 
 `nmr -q <command>` sets it for the run and outranks an inherited value. Both values are spelled out so that either direction is expressible: Export `NMR_COMMAND_VERBOSITY=quiet` for a quiet shell, and set `full` on one invocation to opt back out.
 
 `NMR_OUTPUT_STYLE` is nmr's own as well, and sets the style in which nmr renders every marker that it prints; see [output style](#output-style) below.
 
-`NMR_REPORT_FORMAT` is nmr's own as well, and sets how nmr renders its own verdicts. Its values are `text` and `json`; nmr reports any other non-empty value and exits 1, and an empty value reads as unset. `--json` sets it for the run and outranks an inherited value, and both values are spelled out so that either direction is expressible: Export `NMR_REPORT_FORMAT=json` for a shell whose consumer parses, and set `text` on one invocation to opt back out. The format has two sources, then, whereas a verbosity has four: It does not have a repo-level default or harness detection, because detection would hand every agent JSON in place of the prose that the [bundled guidance](../README.md#agent-guidance) teaches. See [reporting for a machine](#reporting-for-a-machine) for what the objects contain.
+`NMR_REPORT_FORMAT` is nmr's own as well, and sets how nmr renders its own verdicts. Its values are `text` and `json`; nmr reports any other non-empty value as a usage error and exits 2, and an empty value reads as unset. `--json` sets it for the run and outranks an inherited value, and both values are spelled out so that either direction is expressible: Export `NMR_REPORT_FORMAT=json` for a shell whose consumer parses, and set `text` on one invocation to opt back out. The format has two sources, then, whereas a verbosity has four: It does not have a repo-level default or harness detection, because detection would hand every agent JSON in place of the prose that the [bundled guidance](../README.md#agent-guidance) teaches. See [reporting for a machine](#reporting-for-a-machine) for what the objects contain.
 
 `NMR_ENTRY_CHAIN` is nmr's own as well. It lists the commands that the current run has entered and the directories in which it entered them, and nmr passes it to every process that it starts, so that a process re-entering a command already running in its directory fails instead of repeating without end; see [self-referential entries](scripts.md#three-tier-override-system). Do not set it: nmr reports a value that it cannot read and exits 1.
 
@@ -78,7 +78,7 @@ Because the format is nmr's own reporting, and nmr does not tell the commands th
 
 ### Output style
 
-`--output-style <auto|plain|rich>` sets the style for one invocation, and `NMR_OUTPUT_STYLE` sets it for a shell: `rich` marks each verdict with an emoji, such as ✅ or ❌, and `plain` prints a word in its place, such as `PASS` or `FAIL`, which a reader of a log can search for. `auto`, the default, defers to detection. Any other value is a usage error, and nmr exits with code 1, whichever source named it. The flag outranks the variable, and both accept `auto` as well as a style, so a shell exporting one style is overridable on one invocation in either direction.
+`--output-style <auto|plain|rich>` sets the style for one invocation, and `NMR_OUTPUT_STYLE` sets it for a shell: `rich` marks each verdict with an emoji, such as ✅ or ❌, and `plain` prints a word in its place, such as `PASS` or `FAIL`, which a reader of a log can search for. `auto`, the default, defers to detection. Any other value is a usage error, and nmr exits with code 2, whichever source named it. The flag outranks the variable, and both accept `auto` as well as a style, so a shell exporting one style is overridable on one invocation in either direction.
 
 Detection decides stdout and stderr separately. A stream is plain when `CI` is set to anything other than an empty string or `false`, when the stream is not a terminal, or when `TERM` is `linux`; otherwise it is rich. `--json` output does not contain a marker in either style.
 

package/docs/scripts.md

@@ -198,7 +198,7 @@ The run never enters a package, so per-package `lint:pre` and `lint:post` hooks
 
 `lint:workflows`, a root command, lints the GitHub Actions workflows under `.github/workflows/` with [actionlint](https://github.com/rhysd/actionlint), including its shellcheck pass over every `run:` block, and fails on any finding. A repo without `.github/workflows/` passes. The command runs `nmr-actionlint`, which forwards trailing arguments to actionlint, so `nmr lint:workflows .github/workflows/ci.yaml` lints that file alone; inside `check`, `check:strict`, and `root:check`, the step declines them.
 
-The result does not depend on what the machine has installed. nmr pins actionlint 1.7.12 and shellcheck 0.11.0, downloads each from its upstream GitHub release on first use, verifies it against the SHA-256 recorded in nmr, and caches it under `node_modules/.cache/nmr-tools/` at the monorepo root. The first run therefore needs access to `github.com`, and a failed download or a checksum mismatch fails the command. The pyflakes integration is off. The pins move only with a release of nmr.
+The result does not depend on what the machine has installed. nmr pins actionlint 1.7.12 and shellcheck 0.11.0, downloads each from its upstream GitHub release on first use, verifies it against the SHA-256 recorded in nmr, and caches it once per machine under `$XDG_CACHE_HOME/nmr/tools/`, or `~/.cache/nmr/tools/` when `XDG_CACHE_HOME` is unset or not absolute, so that every worktree on the machine shares one copy. A run first looks in that cache and then in `node_modules/.cache/nmr-tools/` at the monorepo root. When the tool is in neither, the run installs it into the machine cache, or into the monorepo-root cache when the machine cache cannot be written, as in a sandbox that confines writes to the worktree. The first run on a machine therefore needs access to `github.com`, and a failed download or a checksum mismatch fails the command. The pyflakes integration is off. The pins move only with a release of nmr.
 
 The supported platforms are macOS and Linux on x64 and arm64; on any other, the command fails and names the platform. actionlint reads its own configuration from `.github/actionlint.yaml`, through which a repo can ignore a finding.
 

package/docs/utilities.md

@@ -100,8 +100,8 @@ Verify that all publishable workspace packages have a `prepublishOnly` script. E
 ensure-prepublish-hooks
 ```
 
-| Flag                  | Description                   | Default           |
-| --------------------- | ----------------------------- | ----------------- |
-| `--fix`               | Add missing hooks             | —                 |
-| `--dry-run`           | Preview what `--fix` would do | —                 |
-| `--command <command>` | Custom hook command           | `"npm run build"` |
+| Flag                  | Description                   | Default       |
+| --------------------- | ----------------------------- | ------------- |
+| `--fix`               | Add missing hooks             | —             |
+| `--dry-run`           | Preview what `--fix` would do | —             |
+| `--command <command>` | Custom hook command           | `"nmr build"` |

package/docs/vitest.md

@@ -108,18 +108,23 @@ In a repo that has not declared the check, [nmr's readyup kit](../README.md#conf
 
 ## What the config supplies
 
-Two settings that a workspace test runner needs almost universally are part of what the factory produces, so a config file declares neither:
+Three settings that a workspace test runner needs almost universally are part of what the factory produces, so a config file declares none of them:
 
 - **A package outside `node_modules` resolves from source.** Because a cross-package import resolves to the dependency's `.ts` rather than its `dist/`, through the `source` condition declared by its `exports` map, a suite runs without a prior build. The reach is what the boundary names: a workspace package, or one linked into the repo from elsewhere, whose real path is outside every `node_modules`. A package that does not declare a `source` condition is unaffected, and so is every package under `node_modules`, whatever its `exports` map declares.
 - **Git subprocesses are isolated.** Every project loads a setup file that points `GIT_CONFIG_GLOBAL` and `GIT_CONFIG_SYSTEM` at the null device, sets `GIT_CONFIG_NOSYSTEM` and `GIT_ATTR_NOSYSTEM`, and injects `core.excludesFile`, `core.attributesFile`, and `maintenance.auto=false` through `GIT_CONFIG_COUNT` and its key/value pairs, so a test that spawns `git` reads neither the developer's identity, nor a signing config that can block on a passphrase, nor their global ignore rules and attributes, and a command such as `git commit` does not start a detached `git maintenance` process that could still be writing under `.git` when the test removes the repository. Those last two need a step of their own: Because neither path is config-derived, git resolves each from `$XDG_CONFIG_HOME/git/`, or from `~/.config/git/` when that variable is unset, whatever the config variables say. `GIT_CONFIG_GLOBAL` already replaces `$XDG_CONFIG_HOME/git/config`; those two are the rest of what that directory supplies. The system attributes file at `$(prefix)/etc/gitattributes` is not named by any config variable at all, which is what `GIT_ATTR_NOSYSTEM` covers. Redirecting `XDG_CONFIG_HOME` would cover the per-user pair as well, but the setup file does not redirect it, because other tools spawned by a test read that variable for configuration of their own: pnpm fails to start under `XDG_CONFIG_HOME=/dev/null`. An injected key outranks repository-local config, so a repository setting its own `core.excludesFile` is overridden under the isolation; a test needing its own value passes it on the invocation as `git -c core.excludesFile=...`, which outranks the injection. The setup file leads each project's `setupFiles`, ahead of every entry that the layers add, because a shared setup establishes the environment in which the rest run.
+- **Each run has its own temp directory.** The root config loads a global setup that creates a run directory named `nmr-vitest-<pid>-…` under the temp directory in effect at startup, points `TMPDIR` at it, and removes it when the run ends, whether its tests pass or fail. Every worker and every process that a test spawns inherits the variable, so scratch files that a test does not clean up stay out of the shared temp directory, where they would otherwise accumulate across runs and repositories until a tmpfs with a fixed inode count has none left. A run stopped by a signal skips global teardown, so the setup first removes each run directory whose process has exited, and leaves those whose process is still running. Vitest runs a project's own `globalSetup` before the root's, so one that a layer adds through `project` runs outside the run directory.
 
-Both defaults exist because omitting either is silent rather than loud: The tiers still exist and the suite still runs green, testing `dist/` and the developer's git identity instead. Turn either off through its own option, which folds across layers like any other, the last layer to declare it winning:
+The first two defaults exist because omitting either is silent rather than loud: The tiers still exist and the suite still runs green, testing `dist/` and the developer's git identity instead. The third exists because a leak shows up only once the temp directory is full, in whatever command next writes to it. Turn any of them off through its own option, which folds across layers like any other, the last layer to declare it winning:
 
 ```ts
-export default defineVitestConfig({ shouldIsolateGit: false, shouldResolveFromSource: false });
+export default defineVitestConfig({
+  shouldIsolateGit: false,
+  shouldIsolateTempDir: false,
+  shouldResolveFromSource: false,
+});
 ```
 
-`shouldResolveFromSource: false` is for a repo whose own packages declare a `source` condition that it does not want in tests; `shouldIsolateGit: false` is for a suite meant to read the developer's own git configuration.
+`shouldResolveFromSource: false` is for a repo whose own packages declare a `source` condition that it does not want in tests; `shouldIsolateGit: false` is for a suite meant to read the developer's own git configuration; `shouldIsolateTempDir: false` is for a suite whose files must outlive the run in the ambient temp directory.
 
 **Vite replaces its condition defaults rather than extending them.** A config writing `conditions: ['my-condition']` by hand therefore drops `module`, so a dependency exposing a `module` entry falls through to whatever its `exports` lists next. A replaced list still resolves `node` and `development` under Vitest, which is why nothing in a test run reports the loss. Because the factory emits Vite's defaults for each environment, whichever way `shouldResolveFromSource` is set, a layer adding a condition extends a complete list rather than replacing one.
 
@@ -157,7 +162,7 @@ export default defineVitestConfig({ tsconfigPaths: true });
 
 It folds across layers like the other two, the last layer to declare it winning. It does not need an `ssr` counterpart the way a condition does: Because Vite keeps this setting outside its per-environment resolve options, the single key applies to the environment through which a test's own imports resolve.
 
-**It is an opt-in because its silent direction is the reverse of the two defaults'.** Leaving it off fails loudly, with an unresolved import naming the specifier. Turning it on is the silent direction, for a repo that declares `paths` for `tsc` alone: A specifier that resolved through a package's `exports` starts resolving through the alias instead, and nothing in the run reports the switch. A repo that does not declare `paths` is unaffected either way.
+**It is an opt-in because its silent direction is the reverse of the defaults'.** Leaving it off fails loudly, with an unresolved import naming the specifier. Turning it on is the silent direction, for a repo that declares `paths` for `tsc` alone: A specifier that resolved through a package's `exports` starts resolving through the alias instead, and nothing in the run reports the switch. A repo that does not declare `paths` is unaffected either way.
 
 **It requires Vite 8**, the version that introduced `resolve.tsconfigPaths`. nmr declares `vite` as an optional peer at `>=8.0.0 <9`, so a repo that declares a stale `vite` of its own sees a warning at install time. That check does not apply to a repo that does not declare `vite` itself, whose Vite is the one that Vitest brings in: a dependency under Vitest 4 and an auto-installed peer under Vitest 5. Both majors accept Vite 6 and 7: On those, the emitted key does nothing and the aliased import fails exactly as it would with the flag off.
 
@@ -223,7 +228,7 @@ Order matters for `setupFiles`, because a shared setup file establishes the envi
 
 **Do not merge two returned configs.** `mergeConfig(defineVitestConfig(), defineVitestConfig(mine))` looks like the idiomatic recovery and fails at startup: Both sides declare the same four project names, which Vitest rejects with `Project name "unit" ... is not unique`. Layers merge the factory's inputs instead, which is why they yield four projects however many fold.
 
-A config file that omits the shared layer still loses those settings, silently -- Vitest's own resolution contract, not something the factory can intercept. Guard it with a test that fails when a package's suite goes missing, which also catches a shared `exclude` pattern that excludes one package's tests. Source resolution and git isolation do not need such a guard: The factory supplies both, so a config file cannot omit them by forgetting a layer.
+A config file that omits the shared layer still loses those settings, silently -- Vitest's own resolution contract, not something the factory can intercept. Guard it with a test that fails when a package's suite goes missing, which also catches a shared `exclude` pattern that excludes one package's tests. Source resolution, git isolation, and temp-directory isolation do not need such a guard: The factory supplies all three, so a config file cannot omit them by forgetting a layer.
 
 ## What the config excludes
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@williamthorsen/nmr",
-  "version": "0.55.0",
+  "version": "1.0.0",
   "private": false,
   "description": "Context-aware script runner for pnpm monorepos",
   "keywords": [
@@ -80,10 +80,10 @@
     "!docs/*.v*.md"
   ],
   "dependencies": {
-    "@williamthorsen/nmr-core": "0.15.1",
+    "@williamthorsen/nmr-core": "0.16.0",
     "@williamthorsen/toolbelt.errors": "0.9.0",
     "@williamthorsen/toolbelt.filesystem": "0.10.0",
-    "glob": "14.0.3",
+    "glob": "14.0.4",
     "prettier": "3.9.10",
     "prettier-plugin-sh": "0.20.2",
     "taze": "21.3.0",
@@ -91,7 +91,7 @@
   },
   "devDependencies": {
     "@williamthorsen/toolbelt.testing": "0.8.0",
-    "@williamthorsen/toolbelt.vitest": "0.13.1",
+    "@williamthorsen/toolbelt.vitest": "0.13.2",
     "esbuild": "0.28.2",
     "readyup": "0.45.0",
     "tinyglobby": "0.2.17",