-
Notifications
You must be signed in to change notification settings - Fork 553
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
commitizen init doesn't work with pnpm #858
Comments
🎉 This issue has been resolved in version 4.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I'm still getting an error with pnpm on 4.3.0.
|
FWIW, I had this same error when trying to initialize Commitizen on a pnpm workspace. You'll understand why it crashes if you try to run
A workaround for this was, indeed, to set the
Commitizen now initializes without any errors. |
Tried this step but it still doesn't work. Anybody got it working? Hey, the Google Gemini just produced this answer and it works perfectly well !!!
|
I had run the
commitizen init cz-conventional-changelog --save-dev --save-exact
command as per README, but it doesn't work, see a copy and paste of the error from commitizen at the end.Suggestion: when there exists a
pnpm-lock.yaml
file, use pnpm instead of npm.Here's my workaround:
Then add this block to the package.json file:
The
cz
command works as usual from this point.Error from
commitizen init cz-conventional-changelog --save-dev --save-exact
:The text was updated successfully, but these errors were encountered: