@williamthorsen/nmr 2.0.2 → 2.1.0

package/docs/scripts.md

@@ -41,6 +41,17 @@ A script value is a string or an array of steps. Only the built-in defaults and
 
 Each array element is a command name, optionally preceded by nmr's own flags, split on whitespace: `-R test` runs the element in every package, the way `nmr -R test` does. An element containing a quoted argument or shell syntax is rejected when the config loads: Name that command as a script of its own and reference the name.
 
+#### Package order in a fan-out
+
+An `-R` or `-F` fan-out of `build` runs the packages in topological order, so that each package builds after its workspace dependencies. Every other fan-out passes `--no-sort` to pnpm and starts each package's command without waiting for its dependencies to finish theirs: `test`, the `test:*` commands, and `typecheck` read the `dist` that an earlier `build` wrote, not anything that the same command writes in another package. A command that does read what its dependencies' runs of it produce, such as a code generator whose output a dependent package imports, keeps the order once `fanOut.extraSortedCommands` lists it:
+
+```ts
+// .config/nmr.config.ts
+export default defineConfig({ fanOut: { extraSortedCommands: ['generate'] } });
+```
+
+The list adds to `build` and cannot remove it, and a name in it that does not resolve to any command fails when the config loads.
+
 #### Running a step in the background
 
 A composite runs its steps in series. An element declared with `shouldRunInBackground` starts and is left running while the steps after it run:
@@ -125,6 +136,7 @@ A minimal `.config/nmr.config.ts` is in the [README](../README.md#configuration)
 | `delegate`         | `false`                                                                       | Keeps every check on the machine that has the tree, whatever `NMR_DELEGATE` or the [user config](delegate.md#the-user-config) says; a delegation flag still sends a run elsewhere (root config only)                                                                                                                                         |
 | `workspaceScripts` | `Record<string, ScriptValue>`                                                 | Scripts added or overridden in the workspace registry (tier 2)                                                                                                                                                                                                                                                                               |
 | `rootScripts`      | `Record<string, ScriptValue>`                                                 | Scripts added or overridden in the root registry (tier 2)                                                                                                                                                                                                                                                                                    |
+| `fanOut`           | `{ extraSortedCommands?: string[] }`                                          | Commands whose fan-out runs packages in topological order, besides `build`; see [package order in a fan-out](#package-order-in-a-fan-out) (root config only)                                                                                                                                                                                 |
 | `output`           | `{ commandVerbosity?: CommandVerbosity; extraAgentEnvVars?: string[] }`       | How loudly runs report command output; see [configuring](reporting.md#configuring)                                                                                                                                                                                                                                                           |
 | `selfHostedRunner` | `{ exempt: string }`                                                          | Why a qualifying repo keeps CI off the self-hosted runners; stops [nmr's readyup kit](../README.md#conformance-checks) from recommending `CI_RUNS_ON` (root config only). The reason is structural: a circular dependency, a platform or capacity the runners lack, or network reach. A missing tool is installed by a workflow step instead |
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@williamthorsen/nmr",
-  "version": "2.0.2",
+  "version": "2.1.0",
   "private": false,
   "description": "Context-aware script runner for pnpm monorepos",
   "keywords": [
@@ -80,9 +80,9 @@
     "!docs/*.v*.md"
   ],
   "dependencies": {
-    "@williamthorsen/nmr-core": "0.16.1",
-    "@williamthorsen/toolbelt.errors": "0.9.1",
-    "@williamthorsen/toolbelt.filesystem": "0.10.1",
+    "@williamthorsen/nmr-core": "0.16.2",
+    "@williamthorsen/toolbelt.errors": "0.10.0",
+    "@williamthorsen/toolbelt.filesystem": "0.10.2",
     "glob": "14.0.4",
     "prettier": "3.9.10",
     "prettier-plugin-sh": "0.20.2",
@@ -90,13 +90,13 @@
     "unconfig": "7.5.0"
   },
   "devDependencies": {
-    "@williamthorsen/toolbelt.testing": "0.8.1",
-    "@williamthorsen/toolbelt.vitest": "0.13.3",
+    "@williamthorsen/toolbelt.testing": "0.8.2",
+    "@williamthorsen/toolbelt.vitest": "0.13.4",
     "esbuild": "0.28.2",
-    "readyup": "0.45.1",
+    "readyup": "0.46.1",
     "tinyglobby": "0.2.17",
     "typescript": "6.0.3",
-    "vite": "8.3.7",
+    "vite": "8.3.8",
     "vitest": "5.1.0",
     "yaml": "2.9.1"
   },

package/dist/esm/check-cache/config-check-cache.d.ts

@@ -1,17 +0,0 @@
-import type { NmrConfig } from '../types.js';
-/**
- * Rejects a `checkCache` name that does not resolve to any command. Both fields are read by name alone, so a
- * misspelt entry is inert: The command that it meant to name goes on running, indistinguishable from one that
- * cannot be cached at all.
- *
- * Because the test is resolvability rather than membership of the cacheable set, an `excludeCommands` entry
- * written against a name that a later release moves out of the defaults remains valid.
- *
- * Reads nothing while every name resolves in the merged registries, and reads a package's own `scripts` only
- * once a name is missing from them: Those are a resolution tier of their own; a name declared only there is
- * valid.
- *
- * Does nothing outside a monorepo root, where `checkCache` is a key that this tier does not honor. `assertTierKeys`
- * reports that, and of the two messages it is the one that names the real mistake.
- */
-export declare function assertResolvableCheckCacheCommands(config: NmrConfig, configPath: string, baseDir: string): void;