You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The bar package depends on the foo package, and everything works fine.
The problems begin if I manually put into the bar package.json dependencies the foo package, like this:
// bar package.json
{
"dependencies": {
"@org/foo": "*"
}
}
If I run lerna version or lerna publish), the asterisk value is automatically updated with the bumped version, but this is causing a problem because just later, Lerna try to do an npm install, resulting in a no matching version found for the just bumped local package.
? Are you sure you want to create these versions? Yes
lerna info execute Skipping releases
lerna ERR! Error: Command failed with exit code 1: npm install --package-lock-only --ignore-scripts
lerna ERR! npm ERR! code ETARGET
lerna ERR! npm ERR! notarget No matching version found for @org/foo@^0.1.1.
lerna ERR! npm ERR! notarget In most cases you or one of your dependencies are requesting
lerna ERR! npm ERR! notarget a package version that doesn't exist.
My question is, is this the correct approach to this problem? Or is there something else I can do? The goal here is that I want to apply a new version, but without running this installation process (because it will cause the error), or maybe find a way to keep the asterisk into the package JSON.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello Guys,
My environment is like this one:
The
bar
package depends on thefoo
package, and everything works fine.The problems begin if I manually put into the bar
package.json
dependencies thefoo
package, like this:If I run
lerna version
or lerna publish), the asterisk value is automatically updated with the bumped version, but this is causing a problem because just later, Lerna try to do an npm install, resulting in ano matching version found
for the just bumped local package.My question is, is this the correct approach to this problem? Or is there something else I can do? The goal here is that I want to apply a new version, but without running this installation process (because it will cause the error), or maybe find a way to keep the asterisk into the package JSON.
Beta Was this translation helpful? Give feedback.
All reactions