Adding before/after lifecycle hooks about scripty HOT 2 OPEN

I think this seems reasonable, but I'm not sure how/whether the lib needs to implement it, since your various scripts themselves could implement the same thing (depending on your scripting language you could make it invisible from each individual script, too).

That said, if you produced a simple PR that implemented an intelligent hooks/ directory (which got quashed gracefully in the presence of a conflicting package script named hooks:before), then I think that'd be cool. I imagine you'd want before-each, before-all, after-each, and after-all.

from scripty.

👍🏽 I like this. What would be a use case for the *each variant? I think the best way to implement this would in options.

"scripty": {
  "prerun": "hooks:before",
  "postrun": "hooks:after"
}

from scripty.