lerna: TypeError: Cannot read property 'composed' of undefined
For security reasons, I can’t share some debug logs with sensitive material. So areas that have I used REMOVED
Expected Behavior
Running lerna publish
should prompt me for all changes since last release
Current Behavior
Running
npx lerna publish --git-remote upstream --conventional-commits --no-verify-registry --no-verify-access --registry=REMOVED
5 error TypeError: Cannot read property 'composed' of undefined
5 error at new Command (/Users/REMOVED/Projects/REMOVED/components-react/node_modules/@lerna/command/index.js:30:33)
5 error at new VersionCommand (/Users/REMOVED/Projects/REMOVED/components-react/node_modules/@lerna/version/index.js:40:1)
5 error at factory (/Users/REMOVED/Projects/REMOVED/components-react/node_modules/@lerna/version/index.js:37:10)
lerna.json
{
"command": {
"publish": {
"message": "chore: publish"
}
},
"packages": [
"components/*",
"tools/*"
],
"version": "independent"
}
Context
We use a private NPM solution Nexus Repository Manager, which is not 100% a true NPM solution, we are locked to the version of lerna that still uses the no-registry flag. Unless there’s a way around this. With that version, when we run the lerna publish and it fails, it’s very difficult to get it back into a place that it knows there are changes again. It seems lerna thinks it’s published, but it never got to our private server. Any help with this would be appreciated.
Your Environment
Executable | Version |
---|---|
lerna --version |
3.3.2 |
npm --version |
6.4.1 |
node --version |
10.15.0 |
OS | Version |
---|---|
NAME | VERSION |
macOS Mojave | 10.14.4 |
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 16 (5 by maintainers)
Closing the issue, some of the issues I was having was with artifactory setup, it’s been resolved, doing a npm login first, then a lerna publish works perfectly now.