-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[BUG] The plugin stops working completely #334
Comments
I'm getting same after upgrading commitlint from 17 -> 19 |
I am having the same issue, it won't load the config neither as module or commonjs. |
I fixed it by downgrading @commitlint/cli, @commitlint/config-conventional and @commitlint/types to version 18. Clearly an issue with v19. |
I think it will be fixed soon after the release of this PR: conventional-changelog/commitlint#3953 For now, as @geoff-harper and @Noxdor suggested downgrade to the latest stable version as below solve the issue:
|
I have the same issue with the following version... "@commitlint/cli": "^19.3.0", I downgraded to 18.6.1and I do not have the error shown anymore... Any idea when it will the extension will support 19.x ? I need to deliver a cli for a dev team to impose strict version so, I need to see if the update will fit our planning. |
any progress? |
Sorry everyone, I haven't been able to find time to check these issues recently. The plugin seems to work fine in my personal use. I feel like I haven't had any projects that need to use node recently, and I just used the default splicing and filling function to facilitate my git commit message. 🤔 Considering that I don't have time to fix this for now, and this problem seems very serious, I am very much looking forward to and thanking anyone who has tried to fix it to submit a PR, and I will pass it and perform automatic testing. ❤️ Finally, thank you all for liking this plugin. If there is a better and faster way to fix it, I also look forward to your comments! ❤️ |
It seems that commitlint had migrate their code base to ESM. Reading commitlint is not supported since commitlint@19. |
@BabakScript I can reproduce the issue that commitlint config is not read correctly with commitlint@19. But the extesion did not stop working. |
Describe the bug
The plugin stops working completely after upgrading my project with the error below:
I'm using devContainer, PNPM, and node. Whenever I click on the plugin button it shows the error I mentioned in the error box in the vsCode.
Application logs
The text was updated successfully, but these errors were encountered: