Allow a package to have listener scripts run by convention
Description
Following the idea behind npm's run-script command, allow for a "scripts" struct in box.json where the key is a short-name for the script and the value is command string to run through the CommandBox interactive shell.
Users will be able to target a script like so:
Any script whose short name is also the name of an interception point in CommandBox will also be run when the CWD of the shell or running command is that package. This will allow developers to create portable ad-hoc listeners for a package that fire.
If the script fails, no further interceptors or commands in the pipeline should process. For example, if the "prePublish" script executes "testbox run" and the tests fail, the version should not be bumped.tagged, etc.
Following the idea behind npm's run-script command, allow for a "scripts" struct in box.json where the key is a short-name for the script and the value is command string to run through the CommandBox interactive shell.
Users will be able to target a script like so:
Any script whose short name is also the name of an interception point in CommandBox will also be run when the CWD of the shell or running command is that package. This will allow developers to create portable ad-hoc listeners for a package that fire.
If the script fails, no further interceptors or commands in the pipeline should process. For example, if the "prePublish" script executes "testbox run" and the tests fail, the version should not be bumped.tagged, etc.