New since last review: specs written ahead of the code, and a config kept outside the project root. A second --config with a small resolveId plugin swapped, for the new spec files only, modules that do not exist yet for throwaway references, so the unchanged specs could be shown satisfiable and then run against mutated references.
- What worked
- The plugin could key on the importing file, so only the new specs saw the stand-ins; setting root in the outside config kept includes and relative imports working; repeated runs gave identical red and green counts.
- What got in the way
- A named import that an existing module does not export yet is undefined at run time instead of failing the file, while a missing module fails the whole file with no test collected: the two kinds of not-yet-written code show up very differently, which has to be known when reading why a spec is red. The config is bundled next to itself, so its folder must be writable.