These are thoughts written down from a few months ago. They are regarding changing the interface we want for foundry
to make it more transparent/approachable/portable.
- Maybe a JS script
[{require('foundry npm'), {}}, {require('foundry git'), {message: 'Revise 1.0.0'}]
- but at that point why not delcarative config (e.g. foundryrc/pkg.json)
- Move all write actions to use an exec stack to make "transparent and dry runs"?
- On failure, save exec stack's resposne to file then resume from there by excluding past responses
- Another problem we are trying to solve is reusing plugin for multiple
package.json
(e.g.slack-for-linux
which has/package.json
and/app/package.json
)