Called after each command's handler function.
Hook order: 8
Called after the command execution completes, just before the result is returned.
Hook order: 12
Called after the final command string is parsed using the options configuration from plugins and resolved command modules.
Hook order: 5
Called after resolving and importing command modules.
Hook order: 3
Called after each state update during command execution.
Hook order: 10
Called before each command's handler function.
Hook order: 7
Called before the ()
function is executed.
Hook order: 11
Called whenever an error is thrown.
Called before command execution begins.
Hook order: 6
Called whenever a plugin or command intends to exit the process via
()
.
Called before parsing the command string using the options config from plugins and resolved command modules.
Hook order: 4
The command string will be parsed multiple times during a command string's execution. After each command module is resolved and imported, the string will be re-parsed without validation to determine the next token in the command string that represents the next command or subcommand. The parse hooks will not be called during this phase.
After all commands are resolved, the command string will be parsed again,
this time with validation using the options config from all plugins and
resolved commands. This is when the the beforeParse
hook is called.
Called before attempting to locate and import command modules.
Hook order: 1
Called before attempting to locate and import each subcommand module.
Hook order: 2
Called before each state update during command execution.
Hook order: 9
The core hooks interface that defines lifecycle events for the CLI execution process. Hooks are called in sequential order as listed below.