@smoothbricks/nx-plugin 0.7.16 → 0.7.18
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +210 -64
- package/dist/.build-inputs.json +28 -23
- package/dist/bun-lock-scope.d.ts +128 -20
- package/dist/bun-lock-scope.d.ts.map +1 -1
- package/dist/bun-lock-scope.js +267 -44
- package/dist/cargo-closure-input.d.ts +8 -6
- package/dist/cargo-closure-input.d.ts.map +1 -1
- package/dist/cargo-closure-input.js +14 -11
- package/dist/cargo-source-hash.d.ts +23 -4
- package/dist/cargo-source-hash.d.ts.map +1 -1
- package/dist/cargo-source-hash.js +80 -14
- package/dist/cargo-workspace.d.ts +20 -2
- package/dist/cargo-workspace.d.ts.map +1 -1
- package/dist/cargo-workspace.js +42 -22
- package/dist/compile-environment.d.ts +8 -0
- package/dist/compile-environment.d.ts.map +1 -0
- package/dist/compile-environment.js +80 -0
- package/dist/dependency-manifests.d.ts +13 -0
- package/dist/dependency-manifests.d.ts.map +1 -0
- package/dist/dependency-manifests.js +20 -0
- package/dist/ensure-built-receipt.d.ts +3 -2
- package/dist/ensure-built-receipt.d.ts.map +1 -1
- package/dist/ensure-built-receipt.js +3 -2
- package/dist/eslint-config-closure.d.ts +8 -3
- package/dist/eslint-config-closure.d.ts.map +1 -1
- package/dist/eslint-config-closure.js +24 -5
- package/dist/executors/bounded-exec/bounds.d.ts +12 -1
- package/dist/executors/bounded-exec/bounds.d.ts.map +1 -1
- package/dist/executors/bounded-exec/bounds.js +8 -4
- package/dist/executors/bounded-exec/cpu-rise.d.ts +73 -0
- package/dist/executors/bounded-exec/cpu-rise.d.ts.map +1 -0
- package/dist/executors/bounded-exec/cpu-rise.js +111 -0
- package/dist/executors/bounded-exec/executor.d.ts +1 -1
- package/dist/executors/bounded-exec/executor.d.ts.map +1 -1
- package/dist/executors/bounded-exec/executor.js +54 -22
- package/dist/executors/bounded-exec/hang-diagnostics.d.ts +8 -0
- package/dist/executors/bounded-exec/hang-diagnostics.d.ts.map +1 -1
- package/dist/executors/bounded-exec/hang-diagnostics.js +66 -6
- package/dist/executors/bounded-exec/mbx-pool.d.ts +16 -2
- package/dist/executors/bounded-exec/mbx-pool.d.ts.map +1 -1
- package/dist/executors/bounded-exec/mbx-pool.js +18 -2
- package/dist/executors/bounded-exec/mbx-reservations.d.ts +5 -2
- package/dist/executors/bounded-exec/mbx-reservations.d.ts.map +1 -1
- package/dist/executors/bounded-exec/mbx-reservations.js +5 -3
- package/dist/executors/bounded-exec/progress-channel.d.ts +38 -0
- package/dist/executors/bounded-exec/progress-channel.d.ts.map +1 -0
- package/dist/executors/bounded-exec/progress-channel.js +113 -0
- package/dist/executors/bounded-exec/progress.d.ts +2 -1
- package/dist/executors/bounded-exec/progress.d.ts.map +1 -1
- package/dist/executors/bounded-exec/ram-temp.d.ts +24 -1
- package/dist/executors/bounded-exec/ram-temp.d.ts.map +1 -1
- package/dist/executors/bounded-exec/ram-temp.js +123 -16
- package/dist/executors/bounded-exec/schema.d.ts +5 -0
- package/dist/executors/bounded-exec/schema.d.ts.map +1 -1
- package/dist/executors/bounded-exec/schema.js +17 -1
- package/dist/executors/bounded-exec/verdict.d.ts +13 -6
- package/dist/executors/bounded-exec/verdict.d.ts.map +1 -1
- package/dist/executors/bounded-exec/verdict.js +34 -9
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +216 -97
- package/dist/managed-files/files.d.ts +3 -3
- package/dist/managed-files/files.js +3 -3
- package/dist/managed-files/generator.d.ts +5 -1
- package/dist/managed-files/generator.d.ts.map +1 -1
- package/dist/managed-files/generator.js +22 -7
- package/dist/managed-files/render-memo.d.ts +13 -0
- package/dist/managed-files/render-memo.d.ts.map +1 -0
- package/dist/managed-files/render-memo.js +94 -0
- package/dist/test-program.d.ts +11 -6
- package/dist/test-program.d.ts.map +1 -1
- package/dist/test-program.js +39 -35
- package/dist/tool-bins.d.ts +12 -0
- package/dist/tool-bins.d.ts.map +1 -1
- package/dist/tool-bins.js +31 -6
- package/dist/typecheck-route.d.ts +3 -4
- package/dist/typecheck-route.d.ts.map +1 -1
- package/dist/typecheck-route.js +4 -15
- package/dist/typecheck-test-policy.d.ts +10 -1
- package/dist/typecheck-test-policy.d.ts.map +1 -1
- package/dist/typecheck-test-policy.js +40 -24
- package/dist/workspace-index.d.ts +14 -1
- package/dist/workspace-index.d.ts.map +1 -1
- package/dist/workspace-index.js +36 -4
- package/managed/raw/patches/nx@24.0.3.patch +703 -119
- package/managed/raw/patches/{ttsc@0.34.1.patch → ttsc@0.36.3.patch} +728 -71
- package/managed/raw/tooling/direnv/developer-links.ts +17 -3
- package/managed/raw/tooling/direnv/devenv.smoo.nix +1 -1
- package/managed/templates/github/actions/save-nix-devenv/action.yml +19 -1
- package/managed/templates/github/actions/setup-devenv/action.yml +2 -0
- package/package.json +5 -4
- package/src/bun-lock-scope.ts +293 -40
- package/src/cargo-closure-input.ts +19 -11
- package/src/cargo-source-hash.ts +103 -13
- package/src/cargo-workspace.ts +59 -20
- package/src/compile-environment.ts +35 -0
- package/src/dependency-manifests.ts +30 -0
- package/src/ensure-built-receipt.ts +3 -2
- package/src/eslint-config-closure.ts +27 -6
- package/src/executors/bounded-exec/bounds.ts +13 -4
- package/src/executors/bounded-exec/cpu-rise.ts +156 -0
- package/src/executors/bounded-exec/executor.ts +65 -21
- package/src/executors/bounded-exec/hang-diagnostics.ts +88 -6
- package/src/executors/bounded-exec/mbx-pool.ts +24 -3
- package/src/executors/bounded-exec/mbx-reservations.ts +7 -5
- package/src/executors/bounded-exec/progress-channel.ts +129 -0
- package/src/executors/bounded-exec/progress.ts +2 -1
- package/src/executors/bounded-exec/ram-temp.ts +137 -17
- package/src/executors/bounded-exec/schema.ts +19 -0
- package/src/executors/bounded-exec/verdict.ts +44 -16
- package/src/index.ts +272 -106
- package/src/managed-files/files.ts +3 -3
- package/src/managed-files/generator.ts +21 -6
- package/src/managed-files/render-memo.ts +135 -0
- package/src/test-program.ts +36 -41
- package/src/tool-bins.ts +35 -6
- package/src/typecheck-route.ts +5 -14
- package/src/typecheck-test-policy.ts +49 -24
- package/src/workspace-index.ts +40 -5
- package/test-timings.json +6 -0
package/README.md
CHANGED
|
@@ -190,7 +190,13 @@ Fixtures the suite infers in its own process own their Nx state the same way. Th
|
|
|
190
190
|
resolves its own `.nx`. Nx's native file index shares one walk among every context of one workspace-data directory: the
|
|
191
191
|
walk holds `nx_files.lock` there, and a context that waits on it loads the archive that walk wrote instead of walking
|
|
192
192
|
its own root. Resolved through the job's absolute directory, a fixture's context gets the files of whichever root walked
|
|
193
|
-
there last.
|
|
193
|
+
there last. `globIndexedFiles`, `freshIndexedFiles` and `freshIndexedFileData` (`src/workspace-index.ts`) close the same
|
|
194
|
+
hole outside the suite's preload: a root other than this process's workspace is walked under Nx's default data directory
|
|
195
|
+
inside that root, never under the inherited variable. The compiled-in Markdown check's fixtures
|
|
196
|
+
(`tooling/checks/compiled-in-docs.fixtures.ts`) run without the preload; under CI's absolute
|
|
197
|
+
`NX_WORKSPACE_DATA_DIRECTORY` their fixture's walk wrote its archive into the repository's shared directory, and Linux
|
|
198
|
+
CI found no planted crate (run 42738719423), as a walk that waits on the repository's walk and loads its archive would.
|
|
199
|
+
The fixtures plant that variable and require the directory it names to stay empty.
|
|
194
200
|
|
|
195
201
|
Fixture sockets and loopback listeners live where a Cowshed sandbox admits them, never at a literal `/tmp` path or on
|
|
196
202
|
port 0. A fixture's short socket parent alias lives beside the Nx socket directory the job supplies (the parent of
|
|
@@ -461,11 +467,36 @@ this repository once loaded it through one, and the land gate refused the graph)
|
|
|
461
467
|
lock-scope node of the crates the target builds (`cargoClosure` carries it; a target that names neither gets the node of
|
|
462
468
|
the directory it runs in). An entry naming only `cargo-lock:` nodes does not count as naming npm packages.
|
|
463
469
|
|
|
464
|
-
No input declaration removes a
|
|
465
|
-
|
|
466
|
-
|
|
467
|
-
|
|
468
|
-
|
|
470
|
+
No input declaration removes a task's own target from its key. Nx 24.0.3 adds a `ProjectConfiguration` node to every
|
|
471
|
+
task for its own project and for each project its `^` inputs reach (`hash_planner.rs` `gather_self_inputs`). The
|
|
472
|
+
project-configuration hunk of `nx@24.0.3.patch` (`patches/README.md`) hashes that node for the task's own project from
|
|
473
|
+
the project's root, tags and named inputs and the task's own target: its executor, outputs, options, configurations and
|
|
474
|
+
parallelism (not `inputs`, `dependsOn`, `cache` or `//`). For a project the task's `^` inputs reach, the node hashes
|
|
475
|
+
that project's root, tags and named inputs. An edit to one target's command re-keys that target's tasks. Its sibling
|
|
476
|
+
targets, each inferred `cargo-test-*` runner among them, keep their keys unless they read the edited file.
|
|
477
|
+
|
|
478
|
+
That keying is sound only while no executor reads another target's configuration at run time. An executor that does must
|
|
479
|
+
have that target named in the project-configuration hunk, which then hashes it beside the reading task's own target, for
|
|
480
|
+
that executor's tasks only and never for a whole project. The hunk names no target today, because no executor below
|
|
481
|
+
reads one. Every new executor, this plugin's or one a consumer adopts, gets a row here before it runs.
|
|
482
|
+
|
|
483
|
+
| Executor | Reads at run time | Verdict | Evidence |
|
|
484
|
+
| ------------------------------------------ | -------------------------------------------------------------------- | -------- | ---------------------------------------------------------------------------------------------------- |
|
|
485
|
+
| `@smoothbricks/nx-plugin:bounded-exec` | its options, the workspace root, its own task's id and hash | own only | `src/executors/bounded-exec/executor.ts:266-271`, `:337` |
|
|
486
|
+
| `@smoothbricks/nx-plugin:all-verdicts` | its options and the workspace root | own only | `src/executors/all-verdicts/executor.ts:157-166` |
|
|
487
|
+
| `@smoothbricks/nx-plugin:typescript-emit` | its options and the tsconfig they name | own only | `src/executors/typescript-emit/executor.ts:66-68` |
|
|
488
|
+
| `@smoothbricks/nx-plugin:scriptc-native` | its options and the workspace root | own only | `src/executors/scriptc-native/executor.ts:101` |
|
|
489
|
+
| `@smoothbricks/nx-plugin:cargo-zigbuild` | its options and the workspace root | own only | `src/executors/cargo-zigbuild/executor.ts:226-227` |
|
|
490
|
+
| `@smoothbricks/nx-plugin:shard-timings` | its options, its project's name and the workspace root | own only | `src/executors/shard-timings/executor.ts:19-23` |
|
|
491
|
+
| `@smoothbricks/nx-plugin:wrangler-deploy` | its project's root; its hasher reads its own target's `stage` option | own only | `src/executors/wrangler-deploy/executor.ts:25-39`, `src/executors/wrangler-deploy/hasher.ts:102-103` |
|
|
492
|
+
| `nx:run-commands` | its options and its own target's `ultracache` and `continuous` | own only | `nx/dist/src/executors/run-commands/run-commands.impl.js:78` |
|
|
493
|
+
| `nx:run-script` | its options and its project's root | own only | `nx/dist/src/executors/run-script/run-script.impl.js:14` |
|
|
494
|
+
| `nx:noop` | nothing | none | `nx/dist/src/executors/noop/noop.impl.js` |
|
|
495
|
+
| `@nx/js:verdaccio` | its options and the workspace root | own only | `@nx/js/dist/src/executors/verdaccio/verdaccio.impl.js:30`, `:55` |
|
|
496
|
+
| A consumer's local plugins (`createNodes`) | nothing at run time: they shape targets while the graph is built | n/a | a derived target's options are part of its own configuration, so its own key carries them |
|
|
497
|
+
|
|
498
|
+
A test or script that reads its own package's targets (`package.json` `nx.targets`) keys that `package.json` as a file
|
|
499
|
+
input; a check that reads the whole graph keys `{workspaceRoot}/**/*` or a runtime key of the graph it reads.
|
|
469
500
|
|
|
470
501
|
Workspace policy defaults non-production tasks to `["{projectRoot}/**/*", "!{projectRoot}/**/*.md"]`, without a forced
|
|
471
502
|
CI workflow input. It migrates the old CI-only `sharedGlobals` reference out of `default` and never re-injects that
|
|
@@ -710,9 +741,11 @@ computed paths and arbitrary build-script reads still need explicit inputs. A co
|
|
|
710
741
|
file index holds both it and the source including it: an ignored one is a build output, whose bytes no fileset can hash
|
|
711
742
|
and which reaches consumers through its producer's dependency outputs. Naming it would only key the project graph on the
|
|
712
743
|
names the last producer run left on disk, so a run regenerating content-named files would move every key it was hashed
|
|
713
|
-
under.
|
|
714
|
-
|
|
715
|
-
|
|
744
|
+
under. The scan reads a package's Rust sources and nested packages from that same index, and reads a source's text only
|
|
745
|
+
when Nx's content hash of it is one no earlier scan saw: an unchanged tree's recomputation reads no Rust source and
|
|
746
|
+
lists no directory. External path-package digests include the same literal data bytes. Inferred `napi-*` and
|
|
747
|
+
repository-root `cargo-wasm` builds use this resolved closure rather than every Rust file in the workspace, while
|
|
748
|
+
retaining their toolchain pins, wrapper scripts, N-API configuration and CLI version.
|
|
716
749
|
|
|
717
750
|
Runtime file identities are rooted in Cargo package name/version and the declared input role, not in the consuming
|
|
718
751
|
checkout's absolute path or depth. Source paths are package-relative; compiled-in data keeps its declaring source and
|
|
@@ -856,12 +889,33 @@ change re-keys the tasks that can load what changed and no other.
|
|
|
856
889
|
|
|
857
890
|
- `bun-lock:<projectRoot>`, one per `package.json` project (`bun-lock:.` for the root manifest). Its edges, added by the
|
|
858
891
|
plugin's `createDependencies`, go to the npm nodes the manifest's dependencies resolve to (resolved exactly as Nx
|
|
859
|
-
resolves a project's own package edges)
|
|
860
|
-
|
|
861
|
-
|
|
862
|
-
node to the packages it depends on and hashes each by the integrity
|
|
863
|
-
|
|
864
|
-
|
|
892
|
+
resolves a project's own package edges) and to the runtime node (`bun-lock-runtime:<projectRoot>`) of each workspace
|
|
893
|
+
member it depends on: the closure of that member's `dependencies`, `optionalDependencies` and `peerDependencies`,
|
|
894
|
+
which a dependent loads through it, so a member's devDependencies key only its own targets. Nx's lockfile parser links
|
|
895
|
+
every versioned npm node (`npm:<name>@<version>`) to the packages it depends on and hashes each by the integrity
|
|
896
|
+
bun.lock records. It also publishes a hoisted package as `npm:<name>` with no edges, and Nx's locator resolves a
|
|
897
|
+
declaration or an import to either name, so the plugin links each such alias to its versioned node: a key on either
|
|
898
|
+
holds the package's closure, and the undeclared-import check compares packages by name and version. The node keys a
|
|
899
|
+
target on the closure its manifest reaches. A member's node has no edge to the root's. Bun's isolated linker links
|
|
900
|
+
into a directory's `node_modules` exactly what its manifest declares, but Node's lookup from a member goes on into the
|
|
901
|
+
root's, so a member can load anything the root declares. Two rules make the member's own closure the whole of what its
|
|
902
|
+
targets load:
|
|
903
|
+
- `createMetadata` refuses the graph when a member's sources import a package its node does not reach (Nx's own
|
|
904
|
+
`static` and `dynamic` edges to npm nodes), naming the member and the package. Declaring the package in the member's
|
|
905
|
+
`package.json` puts it in the member's closure.
|
|
906
|
+
- A tool a target runs keys each package it loads by name by the scope that declares it where it loads: the nearest
|
|
907
|
+
manifest at or above the loading directory that declares the package. A member's declaration is keyed by its node,
|
|
908
|
+
the root's by the package itself, since the root's node would key all of the root's tooling. Every inferred
|
|
909
|
+
TypeScript target (`tsc-js`, `typecheck`, `typecheck-tests`, `lint`) names its project's node, the `@types` packages
|
|
910
|
+
the manifests above it declare and `tslib` (TypeScript loads both by ancestry), and the packages holding the
|
|
911
|
+
installed configs its `tsconfig` chain extends. `tsc-js` adds `typescript` (ttsc loads the project's compiler API),
|
|
912
|
+
`ttsc` and `@typescript/native` (run from the root's `node_modules/.bin`), and each transform plugin its configs
|
|
913
|
+
name. `lint` adds `eslint` and `@biomejs/biome` when it runs them, and every package the ESLint configs load by
|
|
914
|
+
name.
|
|
915
|
+
|
|
916
|
+
An edit to a package only the root's tooling reaches, such as a dependency of an Nx generator, re-keys the root's
|
|
917
|
+
targets and no member's.
|
|
918
|
+
|
|
865
919
|
- `cargo-lock:<directory>`, for the crates under a directory: its hash digests, per Cargo workspace, every package of
|
|
866
920
|
the locked resolve closure of those crates (a locked package by Cargo package id and source, a path package by name,
|
|
867
921
|
each with what its dependencies resolved to). `cargoClosure` names its project's node; each `cargo-test-*` runner
|
|
@@ -874,10 +928,18 @@ A hand-written target names the same nodes in its `externalDependencies`:
|
|
|
874
928
|
```
|
|
875
929
|
|
|
876
930
|
A `cargo-lock:` node exists when an input of a `package.json` project names it (inferred or declared), computed from the
|
|
877
|
-
Cargo resolves the plugin already holds.
|
|
878
|
-
|
|
879
|
-
|
|
880
|
-
|
|
931
|
+
Cargo resolves the plugin already holds. A target that names no `externalDependencies` at all is still keyed on every
|
|
932
|
+
package in every lockfile (`AllExternalDependencies`), the Cargo nodes included.
|
|
933
|
+
|
|
934
|
+
Every `package.json` project defines the named input `bunLockScope` as its own node
|
|
935
|
+
(`[{ "externalDependencies": ["bun-lock:<projectRoot>"] }]`). `externalDependencies` takes no `{projectRoot}` token, so
|
|
936
|
+
a workspace-wide named input or target default names `bunLockScope` to key each project's targets on its own closure; Nx
|
|
937
|
+
resolves a named input from the project first and `nx.json` second. A workspace defines it in `nx.json` as `bun-lock:.`
|
|
938
|
+
for the projects no `package.json` stands for, whose lookup ends in the root's `node_modules`:
|
|
939
|
+
|
|
940
|
+
```json
|
|
941
|
+
{ "namedInputs": { "bunLockScope": [{ "externalDependencies": ["bun-lock:."] }] } }
|
|
942
|
+
```
|
|
881
943
|
|
|
882
944
|
The root project owns the lockfiles, so its `default` fileset holds them. Its versionless check inputs exclude
|
|
883
945
|
`bun.lock`, `bun.lockb` and `Cargo.lock`; the nodes key what they decide.
|
|
@@ -1279,6 +1341,12 @@ Concrete targets come from concrete files:
|
|
|
1279
1341
|
and never compiles one, and the inference guesses no workspace target. A declaration of another shape refuses the
|
|
1280
1342
|
inference by its manifest path. Its compiler is the installed ttsc, which `bun.lock` and the patches in the check
|
|
1281
1343
|
inputs already key. A project that depends only on typia stays on the pinned compiler.
|
|
1344
|
+
- A direct dependency whose ttsc plugin lowers by environment variables declares them in its manifest,
|
|
1345
|
+
`"smoo": { "compileEnv": ["NODE_ENV"] }` (`@smoothbricks/lmao-ttsc` does: it compiles trace statements away unless
|
|
1346
|
+
`NODE_ENV` is `test`). The transformed JavaScript is then a function of those variables, so `tsc-js` and every scriptc
|
|
1347
|
+
target hash each as an `{ "env": … }` input; `typecheck` does not, as no check reads them. A declaration of another
|
|
1348
|
+
shape refuses the inference by its manifest path. Targets a project declares itself, and test targets, list the input
|
|
1349
|
+
in their own `inputs`.
|
|
1282
1350
|
- `typecheck-tests` is inferred from `tsconfig.test.json` and runs the same compiler on
|
|
1283
1351
|
`-p tsconfig.test.json --noEmit`. It first rebuilds the current package's `tsc-js` output (or its non-TypeScript
|
|
1284
1352
|
`build`) so self-imports resolve from its own outputs. Transform calls in test files are checked when the test runner
|
|
@@ -1297,10 +1365,17 @@ Concrete targets come from concrete files:
|
|
|
1297
1365
|
that key in the target directory it built. Nx cache restoration must never replace Cargo's `target` link. Its inputs,
|
|
1298
1366
|
like every cargo-derived fileset, are anchored at `{workspaceRoot}`: Nx resolves a `{projectRoot}` glob against only
|
|
1299
1367
|
the files its project owns, and a nested package owns the crates under it, so a root workspace's test build spelled
|
|
1300
|
-
that way hashes none of its members and replays stale binaries against edited crates.
|
|
1301
|
-
|
|
1302
|
-
that
|
|
1303
|
-
|
|
1368
|
+
that way hashes none of its members and replays stale binaries against edited crates. The test build, `cargo-lint`,
|
|
1369
|
+
the cross check and archives, mutation and bench also hash the outputs of the producers a repository adds to their
|
|
1370
|
+
`dependsOn` that a compile can read: one `{dependentTasksOutputFiles: "<fileset>", transitive: false}` per positive
|
|
1371
|
+
file set of that union, its `{workspaceRoot}/` anchor dropped because Nx matches the glob against each output's
|
|
1372
|
+
workspace-relative path. A generated crate source, a compiled-in file or a manifest a producer writes keys them; a
|
|
1373
|
+
producer's output anywhere else, such as a TypeScript package's `dist`, keys none of them. The test build (`record`)
|
|
1374
|
+
and every runner, each crate's pieces and the serial groups (`target-dir` in the command, `ensure` in the fixture),
|
|
1375
|
+
key the local nextest helper they run (`**/dist/bin/<platform>/smoo-nx-nextest-binaries`) where the workspace builds
|
|
1376
|
+
it. Each member crate gets a cached `cargo-test-<package>` run (30s slow-test warning, no per-test kill) whose inputs
|
|
1377
|
+
include the crates Cargo builds for that crate's tests (from Cargo's locked resolve: its dependencies and its own
|
|
1378
|
+
dev-dependencies, never the dev-dependencies of the crates below it), and whose command runs
|
|
1304
1379
|
`cargo --frozen nextest run --binaries-metadata … --cargo-metadata … --target-dir-remap … --workspace-remap . -E 'package(<crate>)'`
|
|
1305
1380
|
in place, against the binaries the build left in Cargo's target directory. Runners therefore execute rather than
|
|
1306
1381
|
build: they compile nothing in cargo's build tree, copy nothing, and fan out instead of chaining. A test archive
|
|
@@ -1326,10 +1401,11 @@ Concrete targets come from concrete files:
|
|
|
1326
1401
|
so one cache entry serves every checkout of the same commit; nextest re-points
|
|
1327
1402
|
`CARGO_BIN_EXE_<name>`/`NEXTEST_BIN_EXE_<name>` at the remapped binaries at runtime, but a test that reads them
|
|
1328
1403
|
through the compile-time `env!` macro keeps the producing tree's path. Per-crate runners accept an empty nextest
|
|
1329
|
-
selection because a valid workspace member may have no tests and a hash partition may legitimately be empty.
|
|
1330
|
-
|
|
1331
|
-
|
|
1332
|
-
`
|
|
1404
|
+
selection because a valid workspace member may have no tests and a hash partition may legitimately be empty. No Rust
|
|
1405
|
+
test runner waits on `napi-debug`: a test binary loads no debug addon, and a test that runs the package's JavaScript
|
|
1406
|
+
loads the host addon `napi-native` writes, which the runner names itself; only a target that sets `NAPI_DEBUG_ADDON=1`
|
|
1407
|
+
reads `napi-debug`'s (below). A crate declaring `[package.metadata.smoothbricks.wasm-bindgen]` also receives the
|
|
1408
|
+
cacheable `cargo-wasm` output target in its owning project.
|
|
1333
1409
|
- The plugin's own `nextest.toml` is passed as
|
|
1334
1410
|
`--tool-config-file "smoo:$PWD/<to workspace root>/node_modules/@smoothbricks/nx-plugin/nextest.toml"`, so it is a
|
|
1335
1411
|
layer BENEATH the repository's `<cargo-workspace>/.config/nextest.toml` rather than a replacement for it: a repository
|
|
@@ -1457,21 +1533,43 @@ this local relationship explicit for inferred `tsc-js` targets that also have in
|
|
|
1457
1533
|
JavaScript targets with another platform prerequisite must likewise declare that local edge themselves.
|
|
1458
1534
|
|
|
1459
1535
|
A self-hosted workspace that owns the plugin's cowshed dependency builds its declared `napi-native` and independent
|
|
1460
|
-
`lineage-js` producers before **every bounded-exec task
|
|
1461
|
-
|
|
1462
|
-
|
|
1463
|
-
|
|
1464
|
-
|
|
1465
|
-
|
|
1466
|
-
|
|
1467
|
-
|
|
1468
|
-
|
|
1469
|
-
|
|
1470
|
-
|
|
1471
|
-
the
|
|
1472
|
-
|
|
1473
|
-
|
|
1474
|
-
|
|
1536
|
+
`lineage-js` producers before **every bounded-exec task that runs as an mbx Cargo leaf**: a command whose runner Cargo
|
|
1537
|
+
builds (`cargo test`, `cargo nextest run` without `--binaries-metadata` or `--archive-file`, `cargo mutants`), as the
|
|
1538
|
+
executor classifies it (`runsAsCargoLeaf`, from the command line `boundedCommand` composes, in the declaration's or the
|
|
1539
|
+
inference's options or any configuration's). Only such a leaf's admission wait is read from mbx's activity report and
|
|
1540
|
+
its waiters' native lineage, the one load of cowshed's `process-lineage` entry and its addon (specs/cowshed/11_shell.md,
|
|
1541
|
+
"Cargo test-runner boundaries"); a Bun suite, a script or a nextest run of prebuilt binaries is reserved instead and
|
|
1542
|
+
never loads them, so it takes no edge. What the observer reads decides only whether that wait is credited against the
|
|
1543
|
+
idle bound (Bounded exec key, below), so no bounded target keys the addon or lineage bytes for it: a command that itself
|
|
1544
|
+
reads a producer's output depends on that producer and keys its output, as cowshed's Cargo runners do for the `dist/ts`
|
|
1545
|
+
entry and host addon their Node embedder loads (`nx.json` `targetDefaults`). Native tool discovery resolves the local
|
|
1546
|
+
owner from the linked package manifest, not a repository path or project-name alias; an installed consumer takes no
|
|
1547
|
+
local producer edge because its package ships the addon and lineage entry. The plugin's compile and typecheck targets
|
|
1548
|
+
require only `lineage-js`, never the addon or cowshed's full API build. Its runtime-only cowshed project dependency is
|
|
1549
|
+
excluded from ordinary caret build edges, avoiding the executor bootstrap cycle. Declarations that replace `dependsOn`
|
|
1550
|
+
keep the inferred preconditions with Nx’s `"..."` token. When a declaration changes an inferred executor to
|
|
1551
|
+
bounded-exec, its compatible inferred base contains only these runtime prerequisites; the incompatible executor’s
|
|
1552
|
+
command and inputs do not leak across the normal Nx override. The canonical dependency-free `release-check` is the
|
|
1553
|
+
exception: it judges already assembled shipping artifacts and verifies the addon is present, without compiling at
|
|
1554
|
+
runtime or disabling the observer (specs/cowshed/06_cli.md, `release-check`).
|
|
1555
|
+
|
|
1556
|
+
A target of a napi package whose run sets `NAPI_DEBUG_ADDON=1`, in its declaration or inference, loads the package's
|
|
1557
|
+
dev-profile addon from `napi-debug`'s `.cache/native-debug`: it depends on `napi-debug` and keys
|
|
1558
|
+
`{dependentTasksOutputFiles: "**/*.node", transitive: false}`.
|
|
1559
|
+
|
|
1560
|
+
<a id="smoo/nx-plugin!n/executor-build-edge"></a>A self-hosted workspace that owns this plugin's package also orders
|
|
1561
|
+
**every target that runs one of the plugin's executors**, in every project but the plugin, after the plugin's own
|
|
1562
|
+
`build`. An executor is a file that build writes (`dist/executors/<name>/executor.js`), so a task that starts before it
|
|
1563
|
+
ends loads the dist a previous build left, which lacks an executor the plugin gained since: a checkout restored from a
|
|
1564
|
+
cache that predated `cargo-zigbuild` failed `Could not resolve "./dist/executors/cargo-zigbuild/executor.js"` on
|
|
1565
|
+
`cli-x64-linux` while `nx-plugin:build` was still restoring it. The edge is one rule, inferred for declared and inferred
|
|
1566
|
+
targets alike (`{ "projects": ["<the plugin's project>"], "target": "build" }`), never written per executor or per
|
|
1567
|
+
target. Three things take none: the executors the plugin's own build runs (`typescript-emit` and `scriptc-native`, which
|
|
1568
|
+
load from the dist an earlier build left, so waiting for that build would be a cycle), the plugin's own targets (its
|
|
1569
|
+
graph orders them), and the canonical dependency-free `release-check`. An installed plugin ships its executors built, so
|
|
1570
|
+
a consumer takes no edge. Declarations that replace `dependsOn` keep it with Nx's `"..."` token. N-API binaries are not
|
|
1571
|
+
prerequisites of TypeScript declaration emission, so compiler targets do not pull them in by default. Aggregate `build`
|
|
1572
|
+
remains the package-completeness boundary and includes every published local output family.
|
|
1475
1573
|
|
|
1476
1574
|
Do not use colon-style Nx target names such as `build:wasm` or `lint:fix`. Nx CLI syntax already uses colons for
|
|
1477
1575
|
`project:target:configuration`, so colon target names are hard to read, easy to confuse with configurations, and awkward
|
|
@@ -1844,6 +1942,16 @@ The Nx patch repairs upstream Nx runtime behavior, separately from this plugin's
|
|
|
1844
1942
|
which untars the artifact with its stored mtimes and restores it with the same copy. Restoring one directory output of
|
|
1845
1943
|
10,000 1 KiB files took a median 3.4 s for the native remove and copy and 0.79 s more for the stamp, on a machine at
|
|
1846
1944
|
load average 70–120. Not yet proposed upstream.
|
|
1945
|
+
- **A cache hit writes only the outputs that changed, and removes the outputs its entry lacks.** Nx's native restore
|
|
1946
|
+
removed each output and copied it whole, so a hit on outputs that already held the entry's bytes (a run on an input
|
|
1947
|
+
they do not depend on, an output edited and put back) gave every file a new inode and, with the stamp above, a new
|
|
1948
|
+
mtime, and every consumer judging freshness by either redid its work. It also copied only the outputs the entry held,
|
|
1949
|
+
so an output a run on other inputs wrote stayed beside the restored ones. The patched local restore
|
|
1950
|
+
(`restoreChangedOutputs` in `tasks-runner/cache.js`) keeps each output file whose size, mode and bytes match its
|
|
1951
|
+
cached copy and each link with the same target, removes what a cached directory lacks, hands the rest to the native
|
|
1952
|
+
copy output by output, and stamps only those. Every hit, remote included, removes an output its entry lacks. A remote
|
|
1953
|
+
hit still restores each output its artifact holds whole: the native call records the entry's size as the bytes it
|
|
1954
|
+
copies. `nx-cache-restore-mtime.test.ts` holds both. Not yet proposed upstream.
|
|
1847
1955
|
- **A workspace has one daemon, and a second one leaves it alone.** Every daemon overwrote `server-process.json` with
|
|
1848
1956
|
its own pid, so two clients that each found no daemon started two, and the later one displaced the earlier. A client
|
|
1849
1957
|
of the displaced daemon lost its socket mid-request (`EPIPE` on `RECORD_OUTPUTS_HASH_BATCH`) after the run had printed
|
|
@@ -2012,16 +2120,24 @@ line or dot, or a Vitest default-reporter file/test result. Timed Vitest `✓` a
|
|
|
2012
2120
|
duration for skipped files. Reporter headers, failure stack locations and final summary counts do not count. Output that
|
|
2013
2121
|
finishes no test is not progress: the nextest `SLOW` warning, repeated every slow-timeout period for a test still
|
|
2014
2122
|
running, and a hung test heartbeat both keep printing. A suite that keeps finishing tests therefore runs as long as it
|
|
2015
|
-
needs, however slow the host, and a test that never returns ends the run 180 s after the last test that finished.
|
|
2016
|
-
|
|
2017
|
-
|
|
2018
|
-
|
|
2019
|
-
|
|
2020
|
-
|
|
2021
|
-
|
|
2022
|
-
|
|
2023
|
-
|
|
2024
|
-
the
|
|
2123
|
+
needs, however slow the host, and a test that never returns ends the run 180 s after the last test that finished.
|
|
2124
|
+
|
|
2125
|
+
A running test may also report its own progress. Each run with an idle bound is served a progress channel, a Unix socket
|
|
2126
|
+
in a fresh 0700 directory named in the command's environment as `BOUNDED_EXEC_PROGRESS_SOCKET` (`progress-channel.ts`).
|
|
2127
|
+
Each line a client writes there is one record and must be `moved`; the record restarts the bound exactly as a finished
|
|
2128
|
+
test does, and anything else fails the run as a broken reporter. The executor ends its side of a connection when the
|
|
2129
|
+
client ends its own, after reading every record on it, so a client that waits for that end knows its records counted. An
|
|
2130
|
+
agent harness that enforces its own no-progress bound over what its run does reports each movement that check sees, so a
|
|
2131
|
+
long test that keeps moving is not ended for being the last one running. The run's CPU is never a record: a compile
|
|
2132
|
+
inside a test reports nothing and still ends at the bound, where the snapshot names it. bun prints nothing per passing
|
|
2133
|
+
test when it believes an agent runs it, so the executor asks a lone `bun test` for `--dots`, one dot per finished test.
|
|
2134
|
+
Without a recognised execution lifecycle, the clock starts at command spawn; a command that reports no tests makes
|
|
2135
|
+
progress only by exiting. nextest's slow-timeout and the serial groups' code-time classes only warn; no per-test bound
|
|
2136
|
+
kills a test or fails one that passed. Bun has a per-test deadline of its own, 5000 ms unless the command sets one, and
|
|
2137
|
+
it reads no bunfig for it, so every bun leg deletes it with `bun test --timeout=0` (`BUN_TEST_TIMEOUT_FLAG`; `0` means
|
|
2138
|
+
no deadline, measured on the pinned Bun 1.4.2). A test waits for the event it is waiting for, however long a loaded host
|
|
2139
|
+
makes the work take; one that never returns still ends the run through `idleTimeoutMs`. `timeoutMs`, an absolute
|
|
2140
|
+
ceiling, is for commands that report no tests; a target names at least one of the two.
|
|
2025
2141
|
|
|
2026
2142
|
With mbx admission, a supported Cargo/nextest test leaf inherits a private grant pipe: mbx writes `g` on every admission
|
|
2027
2143
|
and `r` on permit drop (`MBX_GRANT_FD=5`). The executor counts overlapping holds: while no hold exists it pauses the
|
|
@@ -2142,8 +2258,11 @@ again. Darwin can answer `EPERM` for an unreaped zombie-only group, and an ambie
|
|
|
2142
2258
|
Failed fixtures retain their cleanup obligation rather than suppressing signal errors.
|
|
2143
2259
|
|
|
2144
2260
|
The final-ten-second pre-signal snapshot attributes the runner's process tree, its leader and leaf call stacks and
|
|
2145
|
-
observed resources, with explicit incomplete/raced results and no delay to termination. Its
|
|
2146
|
-
|
|
2261
|
+
observed resources, with explicit incomplete/raced results and no delay to termination. Its two process censuses, at
|
|
2262
|
+
least five seconds apart inside that window, name each process whose CPU time rose by at least the larger of 0.5 s and
|
|
2263
|
+
twice the coarser resolution of its two readings (two counted seconds where ps counts whole seconds, 0.5 s where it
|
|
2264
|
+
counts centiseconds) and classify the expiry as a build inside the test; CPU never restarts the idle bound. Its timing,
|
|
2265
|
+
visibility and evidence contract is defined in `specs/cowshed/08_testing.md`, "Integration tests (real substrate)".
|
|
2147
2266
|
|
|
2148
2267
|
The snapshot-reset regression orders capture, test completion, and expiry through IPC, not heartbeat cadence. It
|
|
2149
2268
|
deliberately holds the first capture's progress publication while another heartbeat arrives; only the observed PASS
|
|
@@ -2211,7 +2330,14 @@ attach and the lease is still on it. Once the attach is gone the mountpoint is a
|
|
|
2211
2330
|
volume, where a write through `TMPDIR` can make the lease path again, and that free space is not the lease's: the ENOSPC
|
|
2212
2331
|
line then says the lease was lost and why, or that the volume could not be read. Its release says it the same way
|
|
2213
2332
|
(`RAM temp volume: lease <lease> was lost while its task held it: …`) and is never taken as a release of a lease that
|
|
2214
|
-
was there.
|
|
2333
|
+
was there. When the volume itself went from the mountpoint, the disk the lease was taken on can still be attached,
|
|
2334
|
+
mounted nowhere: its mount was lost (on 2026-11-10 a restart of `fseventsd` left the user's 8 GiB disk so, owned by no
|
|
2335
|
+
lease). No path reaches its files and no lease can be taken on it, so that release detaches it, by the registry entry
|
|
2336
|
+
the lease was taken on, through the gateway's `ram-detach` under a detach claim, and its message names the disk, the
|
|
2337
|
+
lost mount and what the detach did; a disk mounted anywhere is left attached and named. A creator that finds the bare
|
|
2338
|
+
mountpoint holding files still refuses to mount over them and touches none of them, but first detaches the disk its
|
|
2339
|
+
ledger records as kept, by that registry entry: what the lost tasks wrote there after the loss never keeps the old disk
|
|
2340
|
+
resident. With no kept record that refusal inspects nothing on the host.
|
|
2215
2341
|
|
|
2216
2342
|
What a command leaves running is ended by its owner, never chosen by where it works (`specs/cowshed/11_shell.md`,
|
|
2217
2343
|
"Process identity and signal ownership"; `specs/cowshed/07_api.md`, `JobSubtreeHandle`). When the job's supervisor
|
|
@@ -2553,13 +2679,18 @@ task id and the hash it ran at:
|
|
|
2553
2679
|
`process aborted with signal 15 (SIGTERM)` (SIGKILL once the force-kill follows); they are the bound's casualties and
|
|
2554
2680
|
do not make the run `failed`. A test that dies of any other signal, or that is aborted with no bound to explain it,
|
|
2555
2681
|
does.
|
|
2556
|
-
- `wedged`: `idleTimeoutMs` fired: no test finished during that much active test
|
|
2557
|
-
interval was exceeded, not that every process stopped: an oversized fixture can
|
|
2558
|
-
the runner reported running (nextest's `SLOW`, libtest's
|
|
2559
|
-
the JUnit report says it aborted when the bound stopped it.
|
|
2560
|
-
|
|
2561
|
-
open-handle evidence, not kernel lock-owner proof. The
|
|
2562
|
-
`lockWaits` is always empty. An incomplete or raced
|
|
2682
|
+
- `wedged`: `idleTimeoutMs` fired: no test finished and no running test reported progress during that much active test
|
|
2683
|
+
time. This proves the completion interval was exceeded, not that every process stopped: an oversized fixture can
|
|
2684
|
+
exceed it too. Its `tests` name those the runner reported running (nextest's `SLOW`, libtest's
|
|
2685
|
+
`has been running for over`) and never finished, and those the JUnit report says it aborted when the bound stopped it.
|
|
2686
|
+
Its `lockWaits` lists only regular files the run holds on numbered descriptors that processes outside the run also
|
|
2687
|
+
hold open, naming those holders' pids and commands. This is open-handle evidence, not kernel lock-owner proof. The
|
|
2688
|
+
open-file census runs only on macOS, so on every other platform `lockWaits` is always empty. An incomplete or raced
|
|
2689
|
+
capture records none. Its `cpuRising` lists each process of the run's tree whose CPU time rose between the snapshot's
|
|
2690
|
+
two process censuses by at least the larger of 0.5 s and twice the coarser resolution of its two readings (2 s at
|
|
2691
|
+
whole seconds, 0.5 s at centiseconds), with its pid, command and gain: a build inside the test, which is a defect and
|
|
2692
|
+
not a hang. It is empty when no process rose or the closing census did not complete, and a record written before it
|
|
2693
|
+
carries none.
|
|
2563
2694
|
- `no-space`: the command failed after its output said a write found no space (`ENOSPC` or `No space left on device`).
|
|
2564
2695
|
Its tests failed on the disk, not on their own, whatever bound or hang followed: it records that line and, when the
|
|
2565
2696
|
task held a RAM lease, the lease, the volume and its free bytes when the line arrived, or why none were read: the
|
|
@@ -2752,8 +2883,9 @@ to the command, which the keyed modules decide. Each entry, and what the executo
|
|
|
2752
2883
|
the run's view of it. Its text is said on stderr and its waiting decides whether the idle bound is credited, which can
|
|
2753
2884
|
fail a run and never changes one that passes. `bounds.js` stays keyed: it decides when a bound fires.
|
|
2754
2885
|
- `hang-diagnostics.js`: the snapshot taken shortly before the no-progress bound fires. It probes with `ps`, `lsof` and
|
|
2755
|
-
`sample`, which suspends the runner for about a second, and signals nothing but its own probes. Its
|
|
2756
|
-
|
|
2886
|
+
`sample`, which suspends the runner for about a second, and signals nothing but its own probes. Its two `ps` censuses
|
|
2887
|
+
are its two CPU samples, paused apart inside its window to be at least five seconds apart. Its text, lock waits and
|
|
2888
|
+
CPU rises are read only once the bound has expired the run, which fails it.
|
|
2757
2889
|
- `testing.js` (and `ensure-built`, whose workspace-root finder it uses, and the producer receipt modules it imports):
|
|
2758
2890
|
the host census the executor quotes when a lease release fails, and the directory a CPU pool binds its socket in. A
|
|
2759
2891
|
directory that cannot be made refuses the run.
|
|
@@ -2885,6 +3017,20 @@ The plugin owns the packaged templates, pure rendering and content-preservation
|
|
|
2885
3017
|
files through Nx `Tree` and uses Nx's resolved project graph for inferred targets. The CLI only supplies the filesystem
|
|
2886
3018
|
and process boundary. There is no separate serialized change plan.
|
|
2887
3019
|
|
|
3020
|
+
A project's TypeScript sources, which decide its `tsconfig.test.json` include, come from Nx's workspace file index for
|
|
3021
|
+
the Tree's root (.gitignore and .nxignore applied) with the Tree's pending edits over it, as devkit's `getProjects`
|
|
3022
|
+
lists project files: one pass over that listing answers every project, so a render lists no directory and probes no
|
|
3023
|
+
file, and a gitignored build output never shapes a committed config. The render (policy, JSON edits, formatter runs) is
|
|
3024
|
+
a function of the derived context, that listing and what it reads through the Tree, and the generator keeps the last
|
|
3025
|
+
one: a later run whose context and listing are equal, and whose every read gives the same bytes, stages that render
|
|
3026
|
+
again rather than rendering. A Tree with pending edits is always rendered. Prettier and Biome read their own
|
|
3027
|
+
configuration from disk, so it is not part of that check; Prettier already holds it for the life of the process.
|
|
3028
|
+
|
|
3029
|
+
The daemon runs a global sync generator on every graph computation and reports what it would change, but only `nx sync`
|
|
3030
|
+
writes it: a task run applies task sync generators alone. A managed file edited in a consuming repository is therefore
|
|
3031
|
+
drift every computation reports and nothing converges until `nx sync` reverts it. Change the packaged template instead,
|
|
3032
|
+
here.
|
|
3033
|
+
|
|
2888
3034
|
The idempotence witness compares the second pass's managed-target roster with the populated first pass before checking
|
|
2889
3035
|
unchanged actions, an empty staged diff and retained bytes. An empty result is not evidence that generation inspected
|
|
2890
3036
|
the managed files.
|
package/dist/.build-inputs.json
CHANGED
|
@@ -15,45 +15,48 @@
|
|
|
15
15
|
"packages/nx-plugin/src/bounded-test-policy.ts": "b52a8858543d25e173aad4f49002a7cdc7f70b098f6046fc56acb747065acd8a",
|
|
16
16
|
"packages/nx-plugin/src/build-state-output-policy.ts": "031a75cb96a2fed0ab2ce80a98588482595f7550d5259e33edabd6e676ad3a3c",
|
|
17
17
|
"packages/nx-plugin/src/built-output-packages.ts": "e593f08d42298c9881d381bb8afbae858108941387f67927d6cc1f49e504e4e2",
|
|
18
|
-
"packages/nx-plugin/src/bun-lock-scope.ts": "
|
|
18
|
+
"packages/nx-plugin/src/bun-lock-scope.ts": "b7534de8bfb54d9f25773678b63a5fd72fce1795b92fdb65868982e13bda6305",
|
|
19
19
|
"packages/nx-plugin/src/cargo-build-script-env.ts": "e5b45ccefc2255cd8a48121eb97132a08e136b4cbbc375d04c940d821a429b23",
|
|
20
|
-
"packages/nx-plugin/src/cargo-closure-input.ts": "
|
|
20
|
+
"packages/nx-plugin/src/cargo-closure-input.ts": "0985e176d9f50df6c65d292754b7ad349f7d6c1cc82680b8dc4a3102f851a992",
|
|
21
21
|
"packages/nx-plugin/src/cargo-dev-profile.ts": "34764ba4fc2aeebe75051c98c2eb64b6baeaa3d8cc0242803081ef935465368d",
|
|
22
22
|
"packages/nx-plugin/src/cargo-retention-hook.ts": "5699506a32aff25be4adca91fff443bea2bfcd6fd7b2964dfa38296c50043ba1",
|
|
23
|
-
"packages/nx-plugin/src/cargo-source-hash.ts": "
|
|
23
|
+
"packages/nx-plugin/src/cargo-source-hash.ts": "c44944cfa42927961fe56abc3de1c4db0e9924d52e11fecc48be7b78b89347bb",
|
|
24
24
|
"packages/nx-plugin/src/cargo-toolchain-paths.ts": "3c622c19ed7a43166e81f9a92e8ab0e3b607690add5408cd96e95912ecf4c4c1",
|
|
25
25
|
"packages/nx-plugin/src/cargo-toolchain-policy.ts": "9c7bae572b57046dcc1e3d577b4abb25e877cf551efcca1b837c4bb5a8c62203",
|
|
26
|
-
"packages/nx-plugin/src/cargo-workspace.ts": "
|
|
26
|
+
"packages/nx-plugin/src/cargo-workspace.ts": "10399b2a285cfa1ec61c3c33cf22e4747506a7d6a8adfe75fc9b45676493ae25",
|
|
27
|
+
"packages/nx-plugin/src/compile-environment.ts": "8085b28e695f60306eefb91f3eca3e1bb908d7ea1676d028c7c85a6adda1a95c",
|
|
27
28
|
"packages/nx-plugin/src/cross-check-policy.ts": "3a22f798805dca09f6452d929d86c0d76621bdd32d5d1f21fe02c75cf7335e2f",
|
|
29
|
+
"packages/nx-plugin/src/dependency-manifests.ts": "2acc8497dbf07e432a1a093c7c2fd8765bc4c3e089be7b332ea7d239e280d0b0",
|
|
28
30
|
"packages/nx-plugin/src/deploy-policy.ts": "2f6202000dceca84d472f417affce50fd2ec3cab87c969443d83ec6e1d4ccf71",
|
|
29
31
|
"packages/nx-plugin/src/disk-command-policy.ts": "fb8731ccf41cff47b88f30165b08dc8d551068c436f4e49cb2b62aa4b49be43c",
|
|
30
|
-
"packages/nx-plugin/src/ensure-built-receipt.ts": "
|
|
32
|
+
"packages/nx-plugin/src/ensure-built-receipt.ts": "f65e7bf7136a252d1780e69e3af57a3a44e01f11bb3441876eef9f6b9ba9e3ed",
|
|
31
33
|
"packages/nx-plugin/src/ensure-built-witness.ts": "428b3bde289d4f10cdc2b2442a84ebc653f3da8955f9ea596dddf3c759029b1c",
|
|
32
34
|
"packages/nx-plugin/src/ensure-built.ts": "5e0a98b9e17a15eadfa79eb53df7e1fc7ef5997b1bf5e2a46a1fceb930e3315c",
|
|
33
|
-
"packages/nx-plugin/src/eslint-config-closure.ts": "
|
|
35
|
+
"packages/nx-plugin/src/eslint-config-closure.ts": "857371ab7fb4f3fac15fc583ec1d755e8f6942ba1ed4a32be3a8292fcd45cece",
|
|
34
36
|
"packages/nx-plugin/src/eslint-file-set.ts": "06d2b6c895c025bfc5269e119830f6fb2c21a6e35dd8e1484ecc8086aa13f753",
|
|
35
37
|
"packages/nx-plugin/src/eslint-sources.ts": "976a2b8e0520b5f6aaf397a272791817a4f385507bc0cbaad4b114fefa8decf5",
|
|
36
38
|
"packages/nx-plugin/src/executors/all-verdicts/executor.ts": "4d3aac65aa2e03a2d24d149c412aa18f2e66a6a36a4e88993122b10e9355c8f0",
|
|
37
39
|
"packages/nx-plugin/src/executors/all-verdicts/schema.ts": "2ca6bd8d2f19d851f291ab6a5227167399b9dc8ed0fda0248b69896d77e471f1",
|
|
38
40
|
"packages/nx-plugin/src/executors/bounded-exec/admission-queue.ts": "86664180f8296032f7c96022a790285799e666d92360a10b7a5cc6f3facd58eb",
|
|
39
|
-
"packages/nx-plugin/src/executors/bounded-exec/bounds.ts": "
|
|
41
|
+
"packages/nx-plugin/src/executors/bounded-exec/bounds.ts": "bd59a97f88851619f64af7adb9f787afee90174c780964200c714eaa81363259",
|
|
40
42
|
"packages/nx-plugin/src/executors/bounded-exec/child-exit-diagnostics.ts": "fdcd4e074577814d9b7b9d014d2c39297e9c763bd570d9fab0db172349e039b2",
|
|
41
43
|
"packages/nx-plugin/src/executors/bounded-exec/cpu-grant.ts": "c5217349c23be537d9b6a0a52445f3ee442402fdbd08f1d33a3095c52051616d",
|
|
42
44
|
"packages/nx-plugin/src/executors/bounded-exec/cpu-pool-thread.ts": "47697a9531df5fd6fcdf4e706fc7e5874bca1717c838496673bf148c691f1e9e",
|
|
43
45
|
"packages/nx-plugin/src/executors/bounded-exec/cpu-pool.ts": "bc122174ccf628b769c73197b7a78987d033b5e7ea6cb5ddbeac384310fdd22a",
|
|
46
|
+
"packages/nx-plugin/src/executors/bounded-exec/cpu-rise.ts": "90b345ad3687813d59e150dd14f91c0adf8da1b8963a3f59f56355ce1f651713",
|
|
44
47
|
"packages/nx-plugin/src/executors/bounded-exec/disk-lease.ts": "1a3f6a6fa590d9a2550490bb6906dc91b6c05fbef235b025eaf257eb5310e92d",
|
|
45
|
-
"packages/nx-plugin/src/executors/bounded-exec/executor.ts": "
|
|
48
|
+
"packages/nx-plugin/src/executors/bounded-exec/executor.ts": "ba7ef3630a49e2ca2b4ce689eb29d6804210833af6927043cce281a7bbef3b1c",
|
|
46
49
|
"packages/nx-plugin/src/executors/bounded-exec/gateway-lease.ts": "f3f73bd92db30e4857f98fb8bd2b9a75b2a5a2a318f094e075ed803c1f9a0117",
|
|
47
|
-
"packages/nx-plugin/src/executors/bounded-exec/hang-diagnostics.ts": "
|
|
50
|
+
"packages/nx-plugin/src/executors/bounded-exec/hang-diagnostics.ts": "ddbfd116357e991000c9a5ae4fad4200e3fb3b88212b0d925d06a9b63455f44e",
|
|
48
51
|
"packages/nx-plugin/src/executors/bounded-exec/host-memory.darwin.ts": "fe89fc99f85f48caec7c614cfd976c362253b9707797c2c849a3aa9664e65dbe",
|
|
49
52
|
"packages/nx-plugin/src/executors/bounded-exec/host-memory.linux.ts": "752519893ed6fc3b9d7d17b0b0801d7103129f7a838743d129057debf043f0c1",
|
|
50
53
|
"packages/nx-plugin/src/executors/bounded-exec/host-memory.ts": "d3eef7fb06bf259f0f7f7dc67fc7f246a39adf5e4e80850fd4565e91626b1ec5",
|
|
51
54
|
"packages/nx-plugin/src/executors/bounded-exec/leaf-peak.ts": "0b1b94992b2cbb9e3759785424ceb202667053c5571edf3a79cdd0b206e54a1d",
|
|
52
55
|
"packages/nx-plugin/src/executors/bounded-exec/lease-wait.ts": "59d8ac94d0b8b75858971c5bb28ee421fca4f7685577274fe8bbaf0c01ba462a",
|
|
53
56
|
"packages/nx-plugin/src/executors/bounded-exec/lock-wait.ts": "b14a23b49759a777f4b3338ced003adaf76837c2c38462458f76a7fef1b95d9e",
|
|
54
|
-
"packages/nx-plugin/src/executors/bounded-exec/mbx-pool.ts": "
|
|
57
|
+
"packages/nx-plugin/src/executors/bounded-exec/mbx-pool.ts": "4181c50a212e649e70b38ff25077aecbdddab0b92c0eb91cc14d873ef0dca4e6",
|
|
55
58
|
"packages/nx-plugin/src/executors/bounded-exec/mbx-queue.ts": "ac309e28e5ee78fa08d628edb00e33532514f7572166770799ae86d468c12b4e",
|
|
56
|
-
"packages/nx-plugin/src/executors/bounded-exec/mbx-reservations.ts": "
|
|
59
|
+
"packages/nx-plugin/src/executors/bounded-exec/mbx-reservations.ts": "d5650230f8f240ec6709a351503eeb6c5f8e576bbd75873eb5209cad918ea867",
|
|
57
60
|
"packages/nx-plugin/src/executors/bounded-exec/memory-retry.ts": "e56fd04f8a8ad03247099a1d005fcbcda6def6aa7656e9515309f6f2438fe88d",
|
|
58
61
|
"packages/nx-plugin/src/executors/bounded-exec/no-space.ts": "ec032968d89f9e853796012705a06c06cfc4da54bf6e6f10a526f98daca3d077",
|
|
59
62
|
"packages/nx-plugin/src/executors/bounded-exec/owned-subtree.ts": "cb5edf2b5fe2c1b5b961f8c0ff16ec7bfae3c22ad75dfd671b74f1a4a865863f",
|
|
@@ -62,21 +65,22 @@
|
|
|
62
65
|
"packages/nx-plugin/src/executors/bounded-exec/peak-waiter.ts": "3d9a60f8e61d160cf4151746c160f836954f57aca896127a5ef9df4d09c26180",
|
|
63
66
|
"packages/nx-plugin/src/executors/bounded-exec/pool-admission.ts": "0cc84dbda8d2cf472a0ee9ec14ab136a219ab2ed223e9769ef45590efbb4b793",
|
|
64
67
|
"packages/nx-plugin/src/executors/bounded-exec/pool-environment.ts": "00046e682376dfabedba3f1743b04656bd6a031b0ac4e594ae47e8f7beb2b68a",
|
|
65
|
-
"packages/nx-plugin/src/executors/bounded-exec/progress.ts": "
|
|
68
|
+
"packages/nx-plugin/src/executors/bounded-exec/progress-channel.ts": "68f51041c095ea334cbe9137cf99884d9a758484491cc4dc3506bfe37c3d327a",
|
|
69
|
+
"packages/nx-plugin/src/executors/bounded-exec/progress.ts": "777c41cafb9ae87db49f588b0378b3bba459080e53c85d8747cae4f2e3cef078",
|
|
66
70
|
"packages/nx-plugin/src/executors/bounded-exec/ram-attach.ts": "865eb5c277d9ab4b258013030938aeee762b731a7298fa8ad3c5eba3026df77a",
|
|
67
71
|
"packages/nx-plugin/src/executors/bounded-exec/ram-detach.ts": "535d26114d14d0d94db76227ea7ba52b1ae0b590d7dbac22993b6796d255e666",
|
|
68
72
|
"packages/nx-plugin/src/executors/bounded-exec/ram-temp-fixtures.ts": "075da4ecfd1cf7dd98fc8c894599dcf2720faba07ac30b8e5592964178849359",
|
|
69
73
|
"packages/nx-plugin/src/executors/bounded-exec/ram-temp-held.ts": "7c32555bc6dab3f767925b55b68684d33a69393050342d06f055fb81e8e5332b",
|
|
70
|
-
"packages/nx-plugin/src/executors/bounded-exec/ram-temp.ts": "
|
|
74
|
+
"packages/nx-plugin/src/executors/bounded-exec/ram-temp.ts": "04d337d46ea375f1947016a21564284e3fa7bbc982b5b4842744fa943d5327fe",
|
|
71
75
|
"packages/nx-plugin/src/executors/bounded-exec/run-cpu-pool.ts": "17148ca7a51aff54d9cbb01db558a828804b158f46e4d3d85d39449d2b644861",
|
|
72
76
|
"packages/nx-plugin/src/executors/bounded-exec/runner-hook.ts": "606eab5db826e571eb15df618315e01cc773d09fd647beb1c00f6434df58ffad",
|
|
73
77
|
"packages/nx-plugin/src/executors/bounded-exec/runner-lifecycle.ts": "b2a7c901296bb6c139909297bbdbab5bd00e94319c022307d006b0e1293f6454",
|
|
74
78
|
"packages/nx-plugin/src/executors/bounded-exec/runner-sizing.ts": "bffd2ba0f80758944ca682838832bdbe20ae12eb9a4f75084a3df82ae7786145",
|
|
75
79
|
"packages/nx-plugin/src/executors/bounded-exec/runtime-pin.ts": "3eb9a8b794da51ffa01723509935f48bfb497fba883518046e74a53209f0eb10",
|
|
76
|
-
"packages/nx-plugin/src/executors/bounded-exec/schema.ts": "
|
|
80
|
+
"packages/nx-plugin/src/executors/bounded-exec/schema.ts": "a35b5fbb55a57c01b45d6245421bc1ee330c4adc48ee770e952cb9e9d05bff56",
|
|
77
81
|
"packages/nx-plugin/src/executors/bounded-exec/test-result-writer.ts": "df7668a11d105a1f88d2187ef8b0edff9db7ba56d8176b5bc35daf1359667637",
|
|
78
82
|
"packages/nx-plugin/src/executors/bounded-exec/test-results.ts": "4f83dc3accd7892f45385796522267adad9401326d0cd9ce4d4e1145b9023577",
|
|
79
|
-
"packages/nx-plugin/src/executors/bounded-exec/verdict.ts": "
|
|
83
|
+
"packages/nx-plugin/src/executors/bounded-exec/verdict.ts": "765bc326882102bf9ca1a74f26946d1b153511c9450d92c869190160624ba764",
|
|
80
84
|
"packages/nx-plugin/src/executors/cargo-zigbuild/executor.ts": "622a5f36897d9eb1f7465654e88f4291aedee9767603028d20c1e819b91d72f4",
|
|
81
85
|
"packages/nx-plugin/src/executors/cargo-zigbuild/schema.ts": "e5cf3b0cc91a2d003a63ca0c9a93f1ec08263469b8a19dbe338b2dc0c0810747",
|
|
82
86
|
"packages/nx-plugin/src/executors/scriptc-native/executor.ts": "4db61da4444d3a30acd3995b6cf53a4bc403a40fe856d88b2c30ce467badbea8",
|
|
@@ -102,12 +106,12 @@
|
|
|
102
106
|
"packages/nx-plugin/src/generators/make-public/schema.d.ts": "5e7bd2f1ce16795df4c919d6d53588ea85b574c84400940b6322275f96f60357",
|
|
103
107
|
"packages/nx-plugin/src/go-tests.ts": "8e356b6ee276e6e836c404353b0ffb5ccec5beb261126f167f730e6e01e9c2b6",
|
|
104
108
|
"packages/nx-plugin/src/graph-input-contract.ts": "8a1aec1294960ae80bcff55a0370c95004a911bf1afe6caa47e666da3baeac43",
|
|
105
|
-
"packages/nx-plugin/src/index.ts": "
|
|
109
|
+
"packages/nx-plugin/src/index.ts": "fb859bfeea798d9251a9fdcb89a9a91304f5dee678595bcddfc00bbe8b47085d",
|
|
106
110
|
"packages/nx-plugin/src/managed-assets.ts": "9cea959c09f3163992e666eecc5a65ec1f1b63c81fc56c5e99088507d02c5e3b",
|
|
107
111
|
"packages/nx-plugin/src/managed-files/ci-workflow.ts": "c48f80cf3b215a8b41fdeb220e653a3a26ee288e833b1bb215f8f15de006e5ae",
|
|
108
112
|
"packages/nx-plugin/src/managed-files/context.ts": "472553c8e15f5bb72f7167ca3f3c5ce5171f479a3cdf2fb4b9f86d1f1addf4bd",
|
|
109
|
-
"packages/nx-plugin/src/managed-files/files.ts": "
|
|
110
|
-
"packages/nx-plugin/src/managed-files/generator.ts": "
|
|
113
|
+
"packages/nx-plugin/src/managed-files/files.ts": "0e4010a194cc3ae89cc05ba1d3482d607fd3e39dd776edf0eaa8e38804e5d897",
|
|
114
|
+
"packages/nx-plugin/src/managed-files/generator.ts": "b3d3bdf6f4c665c649472159595ee094a1b73d729495bbae3695817147487e0c",
|
|
111
115
|
"packages/nx-plugin/src/managed-files/github-runs-on.ts": "a049ca60a79dec57f77e5d18090569a9b8b78818219f236fe352e7705500f531",
|
|
112
116
|
"packages/nx-plugin/src/managed-files/json-edit.ts": "81bc6dd10fffff583cc9f2269f0c2fd2f76b1c5aedbc7d068cf29878371497c2",
|
|
113
117
|
"packages/nx-plugin/src/managed-files/managed-content.ts": "a323dc2facbb555385bd3855215ecb1f84ff5ab6636ba971ad55b9b09dbe0af0",
|
|
@@ -116,6 +120,7 @@
|
|
|
116
120
|
"packages/nx-plugin/src/managed-files/pr-preview-cleanup-workflow.ts": "0f34805a6d737f364c23801da62aefcd4afdc7ba87e911019dd6301be640b385",
|
|
117
121
|
"packages/nx-plugin/src/managed-files/private-npm-policy.ts": "795882f98b2c2434e7c0115e93a7b4c0da6142ae0602274b362893c49a46d5a7",
|
|
118
122
|
"packages/nx-plugin/src/managed-files/publish-workflow.ts": "4cb4a8417f09bbdd2aad1e3b5036d6f88c20c62ad64c3163cd0f0134de3e5170",
|
|
123
|
+
"packages/nx-plugin/src/managed-files/render-memo.ts": "8d1417447c486cf95409bd19d954ff7af7970113858fc64ba073a6c76a784ea6",
|
|
119
124
|
"packages/nx-plugin/src/managed-files/tree.ts": "a6b7dc515796a3824199938ce70af7d2b45347ed32064b487f3d5f381509dc54",
|
|
120
125
|
"packages/nx-plugin/src/manifest-hash.ts": "26cb2598853801cf70785386e1847feba7f04780b43809597004b7fb7ecbc2b6",
|
|
121
126
|
"packages/nx-plugin/src/nextest-code-bound.ts": "e1036934a35f1b65e0f43bddbea259e01a1100e553cdeaefc2db8823a4517340",
|
|
@@ -139,18 +144,18 @@
|
|
|
139
144
|
"packages/nx-plugin/src/task-results.ts": "79aab74e46eacb26bba5d67cfdb2a2eedf0d5c03594e76de6b77e734664555a4",
|
|
140
145
|
"packages/nx-plugin/src/test-backstop.ts": "bd8b27cc05f001e460c29997125f2d7cb07a98ca1ae306f0b0f1884978e247e1",
|
|
141
146
|
"packages/nx-plugin/src/test-clock-policy.ts": "4edaef6535b862a5b4ca19686ad958c4df1986e1f97821a6193d4a99742598e9",
|
|
142
|
-
"packages/nx-plugin/src/test-program.ts": "
|
|
147
|
+
"packages/nx-plugin/src/test-program.ts": "66990382fcd5de584b7e6501cd33eff43b13d6b7a8cf1485fce4ce4ae1094faf",
|
|
143
148
|
"packages/nx-plugin/src/test-timings.ts": "73c2de1b5c0d06a6628d1659727a8504eaf3c21e89fe0a5da969702ba6823ec9",
|
|
144
149
|
"packages/nx-plugin/src/test-walk-policy.ts": "f1c92f1a2ba0c3282abb1706bb637d4b5dc74109edb27f7e41edc14e475bfc91",
|
|
145
150
|
"packages/nx-plugin/src/testing.ts": "ef26d48eb7b90d682778cbbff678c9cc25df57a6775cb58b8c925e8fb829fe6a",
|
|
146
|
-
"packages/nx-plugin/src/tool-bins.ts": "
|
|
151
|
+
"packages/nx-plugin/src/tool-bins.ts": "8c99011ffc03a6e2455729b418ffb69f99621ba237a1fb83eb72b50fc377ffb4",
|
|
147
152
|
"packages/nx-plugin/src/type-guards.ts": "87d87a9bb83f0f4614b9f615d8cc7347772cb1418dc1946978987147c0d6ef0c",
|
|
148
|
-
"packages/nx-plugin/src/typecheck-route.ts": "
|
|
149
|
-
"packages/nx-plugin/src/typecheck-test-policy.ts": "
|
|
153
|
+
"packages/nx-plugin/src/typecheck-route.ts": "90d47be308cb510b252451747d1eaaa2675f79c1687070e39fc7d2578abdb476",
|
|
154
|
+
"packages/nx-plugin/src/typecheck-test-policy.ts": "7d945c6b1e23556154c7585d9e20e14010607a9e456f45c30f72b8812b411e1d",
|
|
150
155
|
"packages/nx-plugin/src/version-actions.cts": "c579ed33d5641bd487024429758582fe1f7bde376cfbd4a4a4325aa70fb71883",
|
|
151
156
|
"packages/nx-plugin/src/wait-why-policy.ts": "f10a5370665c0c38dc778d7532b2cd2b008221efea097b788aeaba8ee63745ea",
|
|
152
157
|
"packages/nx-plugin/src/workspace-config-policy.ts": "6cd57431636ecc08eb550aa6771192fe3800159351d21dbb1057df51f8c3955b",
|
|
153
|
-
"packages/nx-plugin/src/workspace-index.ts": "
|
|
158
|
+
"packages/nx-plugin/src/workspace-index.ts": "176a3ebd62dd2a928d38c2d91e5faa08625b4acb1c1a095718b5aaf1222deabc",
|
|
154
159
|
"packages/nx-plugin/src/workspace-manifest.ts": "44d20244ff5fac9b6397e6c0ce6d9eac25d16f95c6a0c21a8cc70ca17067ce26",
|
|
155
160
|
"packages/nx-plugin/src/workspace-package-policy.ts": "f569ce4e5d27168ea83aa41893573cb869d6f062d37133e95911fdd1d709fa8c",
|
|
156
161
|
"packages/nx-plugin/tsconfig.lib.json": "553a96cc72e10c187d5e7d3da767270d8184ae07929139e417345c770b8d84d1"
|