When authoring or reviewing pull requests, it can become difficult to build a mental model of the effects the changes will have on the types within the respective packages or elsewhere in the monorepo.
To help visualize the effects, it can prove useful to manually generate a declaration file for each package, which would allow diffing between the working and main branches to visualize this.
Adding a proper build:types script for this purpose would be useful. This would be separate from any automated workflows, and is only meant to be run manually if and when needed locally.
A secondary issue came up, however, at the moment of opening this issue, where we had an inaccurately named build:types script which was appropriately renamed to lint:types in #73.