From 6d1454db32dc66e14fa6e6109013edacd911df08 Mon Sep 17 00:00:00 2001 From: "Aaron K. Clark" Date: Tue, 19 May 2026 03:06:15 -0500 Subject: [PATCH] docs(readme): use npm run test:watch instead of npm test -- --watch MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `package.json` exposes a dedicated `test:watch` script that already runs vitest in watch mode (vitest's default when invoked without the explicit `run` subcommand). README's Testing section pointed readers at `npm test -- --watch` — which works (npm forwards the `-- --watch` to the underlying `vitest run` command, where vitest recognises the flag), but it's the awkward route past a purpose- built alias. CONTRIBUTING.md and tests/README.md both correctly point at `npm run test:watch`; aligning README closes the drift so a new contributor's first read isn't a slightly-worse path. No code change; suite unchanged at 614 passed. Co-Authored-By: Claude Opus 4.7 (1M context) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index b6dcf41..c515ad9 100644 --- a/README.md +++ b/README.md @@ -170,8 +170,8 @@ public host — the override exposes Postgres on :5432. ## Testing ```bash -npm test # unit + API suite (mocks the DB; no infra needed) -npm test -- --watch # vitest watch mode +npm test # unit + API suite (mocks the DB; no infra needed) +npm run test:watch # vitest watch mode ``` For integration tests against a real Postgres — see