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
There is a package (packagefoo) which is at 0.0.2 version. It is published to verdaccio. Earlier there was a 0.0.1 published to verdaccio, but it was later purged, and, then the aforesaid version was published.
In the app's package.json in the dependencies, I write as follows:
"packagefoo": "^0.0.1"
I then do an npm install --registry http://localhost:4873 on the project root folder, it says it cannot find 0.0.1 version on the verdaccio server.
Shouldn't this automatically resolve to 0.0.2 version of that package?
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
-
There is a package (
packagefoo
) which is at0.0.2
version. It is published to verdaccio. Earlier there was a 0.0.1 published to verdaccio, but it was later purged, and, then the aforesaid version was published.In the app's package.json in the dependencies, I write as follows:
"packagefoo": "^0.0.1"
I then do an
npm install --registry http://localhost:4873
on the project root folder, it says it cannot find0.0.1
version on the verdaccio server.Shouldn't this automatically resolve to 0.0.2 version of that package?
Beta Was this translation helpful? Give feedback.
All reactions