The launch.json is really cool and I haven't actually used that feature in VSCode yet.

Thinking about it, is there any reason why we can't expand this out to be generic across the project? If it works by configuring jest to work on the current file, and all the packages use jest, the same could apply to them right?

Yeah launch.json is suuuper powerful. All you need to do with this config is hit F5, and it'll pickup and run the tests for the open rule. So nice!

I'm not sure if we can have a single launch config across the entire repo because

1. Each package has its ownjest.config.js, so we need to switch the CWD at launch time to make sure jest runs the correct things.

This is easily solvable if we standardise into a single rootjest.config.js across our packages.
This would also make it so you can runyarn jest in the root and have it automatically run all of the tests in the repo.

2. Each package has its own folder structure.

I don't think that vscode'svariables system supports transforms. This means that you can't arbitrarily transform the current path into a test path for the given package.
Notice how I've hardcoded the rules test folder? We'd probably have to setup 4 launch rules which does this for each of the packages