@williamthorsen/nmr 0.22.0 → 0.23.0

package/README.md

@@ -3,17 +3,19 @@
 Context-aware script runner for pnpm monorepos. Ships an `nmr` (node-monorepo run) binary that provides centralized, consistent script execution across workspace packages and the monorepo root.
 
 <!-- section:release-notes -->
-## Release notes — v0.22.0 (2026-07-31)
+## Release notes — v0.23.0 (2026-08-01)
 
 ### 🎉 Features
 
-- 🚨 **Breaking:** Ship shell and Dockerfile formatting from a shared nmr Prettier config (#540)
+- 🚨 **Breaking:** Close the shared Vitest config's path gaps (#546)
 
-  Adds the ability to format shell scripts and Dockerfiles to `nmr fmt`. `@williamthorsen/nmr` now provides a common config for consistency across projects. Shell fences inside Markdown are now formatted as well. These features are absorbed into `nmr fmt` and `nmr fmt:check`; the `fmt:sh` and `fmt:all` commands are removed.
+  Defines common patterns to determine which files are considered test files and which are subject to code coverage. Consumers that use `defineVitestConfig` benefit from these patterns if they follow naming and file-location conventions.
 
-- 🚨 **Breaking:** Require the monorepo root in the shared root Vitest config (#541)
+### 🐛 Bug fixes
 
-  Modifies the testing configuration so that root-level test runs always cover the repository containing the configuration. The shared root Vitest config now requires a `monorepoRoot` option specifying an absolute path to the repository's own root, in place of the optional search origin. A repository nested inside a parent monorepo fails instead of resolving silently to its parent.
+- Stop rewriting documented commands inside Markdown fences (#549)
+
+  Fixes an issue where `nmr fmt` silently rewrote shell commands documented in a repository's Markdown, leaving usage examples that no longer ran as written. Code fences inside Markdown are now left untouched in any language, withdrawing the fence formatting added in 0.22.0. Fence formatting can be reenabled on selected paths via the config.
 <!-- /section:release-notes -->
 
 ## Installation
@@ -587,6 +589,8 @@ Beyond everything Prettier already handles, this config formats `.sh`, `.bash`,
 
 Shell output matches `shfmt` run with no flags: `binaryNextLine`, `spaceRedirects`, and `switchCaseIndent` are pinned to shfmt's CLI defaults, which the underlying plugin inverts. A repo whose scripts shfmt already formatted sees no diff on adoption.
 
+Code fences inside Markdown are left alone, in every language rather than shell alone. Registering the shell plugin also routes a fence tagged `bash` to shfmt, where a documented command's angle-bracket placeholders are valid redirections: `cmd --type <type> --harness claude` is reprinted as `cmd --type claude <type >--harness`, which still runs but no longer does what it documents. It cannot be narrowed back to shell, because Prettier matches a fence tag against the same `extensions` its file inference reads, so the `.bash` routing a script also claims the tag `bash`.
+
 ### Language scoping
 
 `prettier-plugin-sh` routes 20 further file types to the same shell parser, among them `.gitignore`, `.env`, `.csh`, `.nu`, `.properties`, `.ics`, `.vcf`, `CODEOWNERS`, and `hosts`. Since `nmr fmt` hands git's whole file list to Prettier, registering the plugin as shipped would make every one of them formattable — and the shell parser either fails on them or silently rewrites them. A `.gitignore` pattern such as `a(b)c` fails to parse, and an unquoted `&` in a `.env` or `.properties` value is split across two lines.
@@ -618,7 +622,7 @@ export default definePrettierConfig({
 ### Adoption caveats
 
 - **Indentation follows `.editorconfig`**, as it did under shfmt: Prettier maps `indent_style` and `indent_size` to `useTabs` and `tabWidth`, and the plugin honours both. With no `.editorconfig`, the two disagree — shfmt indents shell with tabs, Prettier with two spaces. Add `indent_style = tab` under `[*.sh]` to keep tabs.
-- **Shell fences in Markdown are formatted**, which collapses hand-aligned comment columns in documentation. Prettier keeps the original text when an embedded snippet fails to parse, so illustrative or truncated fences are safe. Use `<!-- prettier-ignore -->` before a fence whose alignment matters.
+- **Markdown fences stop being tidied.** The carve-out that protects documented shell commands costs the `ts`, `json`, and `yaml` fences their formatting too. Fences already formatted stay as they are, so nothing churns on adoption; new ones are simply left as written. A repo whose docs hold no shell can take them back for the Markdown paths it actually uses: `additionalOverrides: [{ files: ['*.md'], options: { embeddedLanguageFormatting: 'auto' } }]` restores `.md` alone, and the carve-out still covers every other path Prettier reads as Markdown.
 - **Adopting the house options reformats the repo.** `singleQuote`, `trailingComma`, and the rest apply on the first run; review that diff separately from the shell one.
 
 ## Shared Vitest config
@@ -671,6 +675,22 @@ export default defineVitestConfig({
 
 Arrays concatenate rather than replace. `exclude` and `setupFiles` therefore add to what the config already declares, and neither seam can narrow `include` or drop a default exclusion. Adding an `include` pattern through `project` widens all three projects at once, so a file matching it is collected by each and runs three times.
 
+### What the config excludes
+
+Collection skips `**/node_modules/**`, `**/.git/**`, and `**/dist/**`. Coverage skips `**/__{fixtures,mocks,tests}__/**`, `**/index.ts`, `**/mock*.{ts,tsx}`, `**/*.d.ts`, and `**/*.types.ts`.
+
+Because both seams concatenate, a consumer can add an exclusion but never remove one. A pattern therefore earns its place in these lists only by preventing a _silent_ failure, one a consumer cannot self-diagnose. A visible failure, such as a stray file sitting at 0% in the coverage report, is left to the consumer's own `project` seam.
+
+Excluding build output from collection is the clearest case. A build that copies `.ts` sources rather than compiling them puts a second copy of the suite under `dist/`, where it is collected and passes green against stale code, and nothing in the run says so. (`nmr build` emits only `.js` and `.d.ts`, neither of which the include matches, so an nmr-built package was never exposed.) `dist/` is deliberately absent from the coverage list, because build output reaching a coverage report shows up as a diagnosable 0% entry.
+
+#### Where to put fixtures
+
+A `__fixtures__/` directory is excluded from coverage at any depth, so fixture data stops counting against a package's numbers whether or not a test imports it.
+
+Placing it outside `__tests__/` settles a second problem: anything named `*.test.{ts,tsx}` under `__tests__/` is collected and run, whatever it holds, so a fixture carrying that name becomes a failing test. `src/__fixtures__/` resolves both halves; `src/__tests__/__fixtures__/` resolves the coverage half alone.
+
+No collection pattern names fixtures, and that asymmetry is intentional. A coverage exclusion cannot hide a real test, whereas a collection exclusion can; since it could not be removed, a consumer who legitimately keeps a test under `__fixtures__/` would have no recourse.
+
 ### Root-scoped tests
 
 A monorepo's own root-level tests need a second config, because the package config is found by walking up from a package directory:

package/dist/esm/commands/build.js

@@ -33,7 +33,7 @@ export async function buildPackage(packageDir, options = {}) {
 }
 export async function computeBuildHash(packageDir, files, emitConfig, compilerVersion) {
     const hash = createHash('sha256');
-    for (const file of [...files].sort()) {
+    for (const file of files.toSorted()) {
         hash.update(file);
         hash.update('\0');
         hash.update(await readFile(path.join(packageDir, file)));

package/dist/esm/prettier.js

@@ -24,6 +24,25 @@ const DEFAULT_OVERRIDES = [
         files: ['*.json5', '*.jsonc', 'tsconfig.json', 'tsconfig.*.json'],
         options: { parser: 'jsonc', singleQuote: false, trailingComma: 'all' },
     },
+    {
+        files: [
+            '*.livemd',
+            '*.markdown',
+            '*.md',
+            '*.mdown',
+            '*.mdwn',
+            '*.mdx',
+            '*.mkd',
+            '*.mkdn',
+            '*.mkdown',
+            '*.ronn',
+            '*.scd',
+            '*.workbook',
+            'README',
+            'contents.lr',
+        ],
+        options: { embeddedLanguageFormatting: 'off' },
+    },
 ];
 export function definePrettierConfig(options = {}) {
     assertNoReplacement(options);

package/dist/esm/vitest.js

@@ -5,12 +5,13 @@ const APP_PATTERNS = ['**/__tests__/**/*.app.test.{ts,tsx}'];
 const INTEGRATION_PATTERNS = ['**/__tests__/**/*.int.test.{ts,tsx}'];
 const ALL_TEST_PATTERNS = ['**/__tests__/**/*.test.{ts,tsx}'];
 const COVERAGE_EXCLUDE = [
-    '**/__{mocks,tests}__/*',
+    '**/__{fixtures,mocks,tests}__/**',
     '**/index.ts',
     '**/mock*.{ts,tsx}',
     '**/*.d.ts',
     '**/*.types.ts',
 ];
+const BUILD_OUTPUT_EXCLUDE = ['**/dist/**'];
 const PACKAGE_COVERAGE_INCLUDE = ['**/src/**/*.{ts,tsx}'];
 const MISSING_MONOREPO_ROOT = 'defineRootVitestConfig requires `monorepoRoot`, an absolute path to the directory holding pnpm-workspace.yaml. Pass `import.meta.dirname` from the root config.';
 export function defineVitestConfig(options = {}) {
@@ -57,7 +58,7 @@ function buildProjects(overrides, extraExclude, projectRoot) {
         const project = {
             extends: true,
             ...(projectRoot !== undefined && { root: projectRoot }),
-            test: { exclude: [...defaultExclude, ...exclude, ...extraExclude], include, name },
+            test: { exclude: [...defaultExclude, ...BUILD_OUTPUT_EXCLUDE, ...exclude, ...extraExclude], include, name },
         };
         return overrides ? mergeConfig(project, { test: overrides }) : project;
     });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@williamthorsen/nmr",
-  "version": "0.22.0",
+  "version": "0.23.0",
   "private": false,
   "description": "Context-aware script runner for pnpm monorepos",
   "keywords": [