Getting strange error: subject may not be empty [subject-empty]

This started a few days ago all of a sudden.

Here’s the full output:

Command failed with exit code 1: git commit -m "refactor: to use a constant name for the handler fn name"
husky > pre-commit (node v12.16.0)
[STARTED] Preparing...
[SUCCESS] Preparing...
[STARTED] Running tasks...
[STARTED] Running tasks for *.(js|ts)
[STARTED] Running tasks for package.json
[SKIPPED] No staged files match package.json
[STARTED] eslint --fix
[SUCCESS] eslint --fix
[SUCCESS] Running tasks for *.(js|ts)
[SUCCESS] Running tasks...
[STARTED] Applying modifications...
[SUCCESS] Applying modifications...
[STARTED] Cleaning up...
[SUCCESS] Cleaning up...
husky > commit-msg (node v12.16.0)
⧗   input: "refactor: to use a constant name for the handler fn name"
✖   subject may not be empty [subject-empty]
✖   type may not be empty [type-empty]

✖   found 2 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

husky > commit-msg hook failed (add --no-verify to bypass)

If I run exactly the same command from CLI it works just fine:

git commit -m "refactor: to use a constant name for the handler fn name"

Any ideas?

Thanks.