Stacktrace to `runCommand` should not be printed when command fails

[ZainlessBrombie]

When the runCommand exits with a non-zero exit code, an Exception occurs. This exception is not caught, resulting in a long stacktrace in the console, that only points to this plugin itself.
I think the error resulting from execSync should be caught and a simple message Command <command> should be printed. Then the serverless process that triggered the hook should be stopped.

Use case: linting automatically before a deploy/package

[weixu365]

That's a good suggestion. Thanks for the feedback.

[github-actions[bot]]

:tada: This issue has been resolved in version 1.3.1 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket:

[ZainlessBrombie]

That was quick
Thank you very much! :)