-
Notifications
You must be signed in to change notification settings - Fork 915
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RangeError: Invalid count value #476
Comments
for some reason this line https://github.com/marionebl/commitlint/blob/master/%40commitlint/cli/src/help.js#L29 4 + longest - length is |
Just run into this issue today with @commitlint v4.3.0, npm v11.0.0 so it seems to me that the issue is not @commitlint or node version related. Edit: Resolved by downgrading node to v8.12.0. |
@dominikfiala makes sense, I've started to seen this bug after migrated to node 10x from node 8x |
* fix: use correct label for failing empty subjects, see #476 * chore: budge to husky api change * test: adapt to corrected subject message
Fixed via f27e7ac |
Expected Behavior
it should run commitmsg properly
Current Behavior
it throws an error
I'm using
simple-git
to perform this commit:Affected packages
Steps to Reproduce (for bugs)
build(change-log): ${tag}
);commitlint.config.js
```js module.exports = { rules: { 'body-leading-blank': [1, 'always'], 'footer-leading-blank': [1, 'always'], 'header-max-length': [2, 'always', 100], 'scope-case': [2, 'always', 'lower-case'], 'subject-case': [2, 'never', ['sentence-case', 'start-case', 'pascal-case', 'upper-case']], 'subject-empty': [2, 'never'], 'subject-full-stop': [2, 'never', '.'], 'type-case': [2, 'always', 'lower-case'], 'type-empty': [2, 'never'], 'type-enum': [ 2, 'always', [ 'build', 'chore', 'ci', 'docs', 'feat', 'fix', 'perf', 'refactor', 'revert', 'style', 'test', 'migration', 'type', ], ], }, }; ```Context
Your Environment
I'm using
nvm
(0.31.1)macosx
"@commitlint/cli": "7.2.1",
"@commitlint/config-conventional": "7.1.2",
git version 2.19.1
hub version 2.5.1
node v10.12.0
The text was updated successfully, but these errors were encountered: