chore: allow input to be passed in watch mode (#384)

It's still quite frustrating to use, but it's now possible to do simple
stuff (force tests to re-run, for example).

Author: ojeytonwilliams

README.md

@@ -10,3 +10,21 @@ BSD-3-Clause © [freeCodeCamp.org](https://freecodecamp.org)
 [travis-url]: https://travis-ci.com/freeCodeCamp/curriculum-helpers
 [daviddm-image]: https://david-dm.org/freeCodeCamp/curriculum-helpers.svg?theme=shields.io
 [daviddm-url]: https://david-dm.org/freeCodeCamp/curriculum-helpers
+
+## Running tests
+
+To run the tests in watch mode, you can use the following command:
+
+```bash
+pnpm test:watch
+```
+
+This spawns two vitest processes and you can interact with them in the terminal. However, input is passed to the processes in sequence making it tricky to use.
+
+To get a standard vitest interface, you can run the tests separately:
+
+```bash
+pnpm test:unit --watch
+# or
+pnpm test:integration --watch
+```

package.json

@@ -94,7 +94,7 @@
     "lint": "eslint . --max-warnings 0 && prettier --check . && tsc --build",
     "format": "prettier --write .",
     "test": "vitest",
-    "test:watch": "concurrently --prefix none \"pnpm test:unit --watch\" \"pnpm test:integration --watch\"",
+    "test:watch": "concurrently -i --raw --prefix none 'pnpm test:unit --watch' --raw 'pnpm test:integration --watch'",
     "test:unit": "vitest --config vitest.unit.config.mjs",
     "test:integration": "vitest --config vitest.integration.config.mjs",
     "prepare": "husky install",