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
Issue in using workspace: protocol in lerna versioning / publish. #3317
Comments
Hi @HariAbinesh, thank you for opening this issue. I was able to successfully reproduce the problem described above and am currently working on a fix. |
@HariAbinesh this should be resolved in 5.5.1 thanks to @fahslaj |
@JamesHenry unfortunately, #3322 did not solve this issue soundly, and I've met another issue related to this scenario. Error says the following line in const depNode = this.get(depName);
// L80 C37
// TypeError: Cannot read properties of undefined (reading 'version')
const version = depNode.version; I've created a repo to reproduce it: lerna-version-issue |
Same error here. I am not sure what should be the correct behavior, though. The version will be resolved later when the workspace protocol is used. |
I'm having the same issue as well! |
On 5.6.1 the issue remains #3343 |
Issue in using workspace: protocol in lerna versioning.
package A has two dependencies in workspace -> package B , C.
when we modify only package A and trigger lerna version or publish, it fails.
Current Behavior
lerna version / publish throws validation error.
To use the 'workspace:' protocol, ensure that a package with name "${depName}" exists in the current workspace.
Expected Behavior
Lerna version / publish should succeed.
Steps to Reproduce
package A has two dependencies in workspace -> package B , C
modify only package A and try versioning.
Reason
First time, package graph will have all available workspace packages info in its Map.
But after lerna tries to write package json and CHANGELOG, the package graph will only have packages to publish info. so it fails.
Environment
(lerna: 5.5.0 => 5.5.0)
The text was updated successfully, but these errors were encountered: