I have a private dependency on package.json and it should always install the latest version. So instead of the version, it's *
.
"dependencies": {
"@user/package": "*"
}
After the package was updated in npmjs it still installed old version with npm i
if I enter exact version number instead of *
- it installs a fresh version, which was published like a day ago.
I had a similar issue when the version was updated a minute ago at npmjs but now npmjs cache should be expired & updated with the new version, isn't it?
How can I avoid such issue and always get newest versions for everything with *
?
I've tried npm cache verify
npm cache clean --force
. No luck.
Even during initial installation of dependencies it's necessary to use npm update
instead of npm install
.
This question talks more about npm install
vs npm update
npm install vs. update - what's the difference?
Conclusion: The only big difference is that an already installed module with fuzzy versioning ...
- gets ignored by npm install
- gets updated by npm update
Thanks CodeCaster for a link for correct command. But:
The issue is still there. Most of the time, it works every time. But. Just had another update when npm did not resolve to the newest version. Switching values form *
to numbers for now. Seems like a bug for me.