I've come around to this. Turns out it was 12AM (or whatever) and I wasn't thinking about the benefits of lowering the barrier to entry for adding more integration tests, so I'm sorry about that.

If you don't mind, I've got a few housekeeping requests:

1. Rename it to init-board-manifest.js
   • We may want to add other scripts to the fixtures
   • .js extension ensures the linter will pick it up
2. Put init-board-manifest.js in fixtures/bin and wire it up in fixtures/package.json
   • {"bin": {"init-board-manifest": "bin/init-board-manifest.js"}}
   • That way, yarn run init-board-manifest from the top level will be a thing

Then, to address the stuff I brought up in #64, can we more explicitly print out (a prompt would be amazing, but an interactive CLI is a much bigger project) what each setting was for each file? Something like:

please verify the following layer settings are correct

arduino-uno.cmp
> file type:   gerber
> layer type:  top copper

Looks like the current script relies on stdout piping, so that stuff could be fine to send to stderr via console.warn or something