@jterrazz/test 18.0.4 → 18.1.0

package/dist/config.js

@@ -19,10 +19,16 @@ var standard_default = defineStandard({ test: {
 		"mobile",
 		"website"
 	],
-	projects: { unit: {
-		isolate: false,
-		reason: "a module test leaves no state behind in a module, so a worker runs its files in one module graph"
-	} }
+	projects: {
+		lint: {
+			isolate: false,
+			reason: "a lint spec lays its own fixture tree and runs the linters as processes of their own, so a worker runs its files in one module graph"
+		},
+		unit: {
+			isolate: false,
+			reason: "a module test leaves no state behind in a module, so a worker runs its files in one module graph"
+		}
+	}
 } });
 //#endregion
 //#region lint/kit/project/loaded-packages.ts

package/dist/vitest.d.ts

@@ -98,7 +98,10 @@ export declare function job(options?: JobProjectOptions): TestProjectInlineConfi
 //#endregion
 //#region src/specifications/lint/lint.project.d.ts
 /** `lint()`: the rules a project ships, run by the real linters over fixture trees. */
-type LintProjectOptions = SpecificationProjectOptions;
+type LintProjectOptions = SpecificationProjectOptions & {
+  /** `false` shares one module graph per worker (`isolate: false`); for specs that keep no state in a module. */
+  isolate?: boolean;
+};
 export declare function lint(options?: LintProjectOptions): TestProjectInlineConfiguration;
 //#endregion
 //#region src/specifications/mobile/mobile.project.d.ts

package/dist/vitest.js

@@ -378,7 +378,14 @@ function job(options = {}) {
 //#endregion
 //#region src/specifications/lint/lint.project.ts
 function lint(options = {}) {
-	return specificationProject("lint", options);
+	const project = specificationProject("lint", options);
+	return options.isolate === void 0 ? project : {
+		...project,
+		test: {
+			...project.test,
+			isolate: options.isolate
+		}
+	};
 }
 //#endregion
 //#region src/specifications/mobile/mobile.project.ts

package/docs/guides/lint-specs.md

@@ -134,6 +134,10 @@ A preset's own `oxlint` (its plugin, its rulebook) is not run by `presets`: the
 
 A linter that fails and reports no diagnostic is refused in four parts rather than read as a clean tree: a plugin that does not load, a config oxlint cannot build, a checker that cannot start.
 
+### One module graph per worker
+
+The lint project runs a worker's files in one module graph (`isolate: false`), as the standard hands it: each spec lays its own fixture tree and runs the linters as processes of their own, so a file leaves nothing in a module for the next one, and the worker, the framework and the kit load once per worker instead of once per file. A project whose lint specs keep state in a module (a cache, a counter, a stub set at load) states `isolate: true` for its `lint` project in `jterrazz.config.ts`, with its reason.
+
 ### A rule pack: a nested Vitest and a reporter fixture
 
 A package that ships lint rules for other projects proves them by running the real binary on a tree: the spec starts a nested `vitest` over a fixture project (`.fixture(directory(...))`) with a reporter fixture that prints one line per finding, and compares that output whole. A rule alone is `ruleTester()`.

package/docs/start/set-up-a-project.md

@@ -108,7 +108,7 @@ There is one helper per kind (`unit`, `integration`, `component`, `website`, `mo
 | `timeout`             | Raise or lower the 30 s default for this project alone: each test's and each hook's, so the `afterAll` that stops what a slow test started has the same budget |
 | `serial`              | Run the project's files one at a time (`fileParallelism: false`), when they share one server, one file, one app                                                |
 
-`unit()` and `component()` are a pair: `unit()` collects `**/*.test.ts` outside `specs/` and leaves out `**/*.test.tsx`, which `component()` collects. So the suffix beside a file decides which project runs it. `unit()` also takes `roots` when the modules are not at the repository root, and `isolate: false` to run a worker's files in one module graph, only for a project whose tests leave no state behind in a module, and the default `vitestConfig` hands it. `component()` takes the options of the app it renders (`vite`, `wrap`, `viewport`, `clock`, `timezone`, `locale`, `root`), described in [Component specs](../guides/component-specs.md#the-constructor-there-is-none); `mobile()` takes the simulator the run shares ([Mobile specs](../guides/mobile-specs.md#one-session-per-run)).
+`unit()` and `component()` are a pair: `unit()` collects `**/*.test.ts` outside `specs/` and leaves out `**/*.test.tsx`, which `component()` collects. So the suffix beside a file decides which project runs it. `unit()` also takes `roots` when the modules are not at the repository root, and `isolate: false` to run a worker's files in one module graph, only for a project whose tests leave no state behind in a module, and the default `vitestConfig` hands it. `lint()` takes `isolate` too, and the default `vitestConfig` hands it `false` as well, since a lint spec lays its own tree and runs the linters as processes of their own ([Lint specs § One module graph per worker](../guides/lint-specs.md#one-module-graph-per-worker)); `mobile()` keeps every file isolated. `component()` takes the options of the app it renders (`vite`, `wrap`, `viewport`, `clock`, `timezone`, `locale`, `root`), described in [Component specs](../guides/component-specs.md#the-constructor-there-is-none); `mobile()` takes the simulator the run shares ([Mobile specs](../guides/mobile-specs.md#one-session-per-run)).
 
 Every project runs in one group, on the workers the preset sizes ([below](#what-the-preset-sets)): a `website` file takes a worker as a node file does, and the `component` pages run beside them in their one Chromium, as many at once as the run has workers. A project whose files run one at a time (`serial`, and `mobile()` unless it states `serial: false`) runs after that group, in a group of its own, so a simulator never shares its machine.
 

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@jterrazz/test",
-    "version": "18.0.4",
+    "version": "18.1.0",
     "description": "Declarative testing framework for HTTP APIs, CLIs, background jobs, websites, mobile apps, rendered components and the rules a project ships: one entry point, real infrastructure and a real browser, golden-file assertions, plus an oxlint convention plugin.",
     "keywords": [
         "api-testing",
@@ -92,7 +92,7 @@
     },
     "devDependencies": {
         "@hono/node-server": "^2.1.1",
-        "@jterrazz/typescript": "^11.1.0",
+        "@jterrazz/typescript": "^11.2.0",
         "@types/better-sqlite3": "^9.6.0",
         "@types/node": "^26.6.2",
         "@types/pg": "^8.23.1",