-
Notifications
You must be signed in to change notification settings - Fork 1
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
commitlint >= 19
breaks the extension
#753
Comments
Potentially related to alessandrojcm/commitlint-pre-commit-hook#152. |
Thanks for the report! Yes, it looks like this is due to commitlint v19 supporting ESM only. The fix seems straightforward; I'll look to have this fixed in the next day or so. |
Unfortunately this did not work the way I thought it did and I had to revert it due to the issue raised in #755. I have an idea to resolve this again, but will require some more work. |
2.6.0 is now out and should take care of this. Thanks for your patience! |
@joshbolduc, I hate to bring the bad news, but it still seems broken for v19. #784 still doesn't work with extension version 2.6.0 # npm list -g
/opt/conda/lib
├── @commitlint/[email protected]
├── @commitlint/[email protected] And the extension output:
The downgrade to v18.6.3 still works. |
I wanted to add that it worked for me. I checked the extension had updated to v2.6.0, restarted it under the Extensions tab, updated my Thanks. |
Hi!
My
.commitlintrc.js
:Everything went smoothly until I upgraded
commitlint
to v19 (19.0.3, to be more specific).Now my output (as I am typing anything into commit message field of the Git panel) is as follows:1
Footnotes
I have checked that downgrading to
cli==18.6.1
andconventional-config==18.6.2
fixes the problem. ↩The text was updated successfully, but these errors were encountered: