scriptsthat correspond to the interception points in CommandBox. Any script defined there will be ran on during that interception point. This allows you to prescribe arbitrary commands on a package-by-package basis. You may wish to set your package location any time you
bumpa package version or perform a
publish. Below is an example of some
pre. After any package script is run, CommandBox will look for another package script with the same name, but prefixed with
Post. So if you have a package that contains 3 package scripts:
postFoo, they will run in this order.
prePreFoo, it would run prior to
interceptData.and will use "dot notation" for nested structs. You can see if the docs on what intercept data is available to each interception point.
preCommandinterception announcement receives a struct called
commandInfowith a key called
commandStringwhich means your package script can access that via the following environment variable:
env showcommand in your package script to dump out all environment variables to the console.