as always nice catch.  I'm squeamish too.

I'm hacking around the fact that we have automation-tests/package.json which is a subset of the node modules we install at the top level package.json.

The motivation for this was to npm install a more minimal set of packages for automation testing, and to be able to be a little more fancy free with what we depend on in automation tests - both good goals.

When I went and started reusing backend testing libraries (secondary.js) which were written more with the assumption that ALL packages were available, I inadvertently made it so automation tests failed, because they indirectly relied on stuff not in `automation-tests/package.json`

what you see here is a *minimal* patch to undo the damage I did.  But it is a minimal hack - we should figure out a better long term solution (I hope it involves a bit of restructuring of tests) and figure out how testing libraries can use production libraries to share code, but we still can not install the world in order to run tests....