Replies: 1 comment 2 replies
-
Hi @nicojs , there is no lifecycle hook for Lerna version that allows you to inject a script before that installation step. As a workaround, you can use The lerna.json configuration update would look like this: {
...
"command": {
...
"version": {
...,
"npmClientArgs": ["--legacy-peer-deps"]
}
}
} |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It seems that
lerna version
also runsnpm install --package-lock-only --ignore-scripts
during its process. This results in an error since lerna@7, because npm workspaces don't support a peer dep mismatch. I believe the oldlerna bootstrap
command did allow it.See detailed logs
Our versioning workflow pre lerna@7 looked like this:
For step 2, we created a custom script:
"version": "node tasks/bump-peer-deps.js"
in root package.json. In that script we update the peer deps when needed.How can I recreate such a thing in lerna@7?
Beta Was this translation helpful? Give feedback.
All reactions