Argument handling is unhelpful and breaks husky out of the box

I do not use husky, but it has been configured on projects to which I contribute.

As a new user, not breaking the configuration on the use of these, below, would be preferred. (As opposed to being left to troubleshoot a confusing error.)

I'm unsure why a single argument changes the core.hooksPath, especially when the argument is not init or install or anything similar. A common and user-friendly approach is to emit usage when invoked with no argument.

npx husky --version
npx husky version
npx husky --help
npx husky help
npx husky -h

npx husky .. with no argument, appears to do nothing (but silently does something), with exit status 0 -- ?