How to always get newest version when using * instead of version number in package.json?

user_1737158 0
Viewed 13266

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.

npmjs npm npm-install
2 Answers

you can try to install with the packagename@latest keyword, but as far as i know you can only use this keyword in command line interface with npm install --save.

npm install --save mypackage@latest

after reading the doc here https://docs.npmjs.com/files/package.json i found you can write "latest" instead of any version number in a package.json file. This should do the trick.

user_25054270

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.

user_17371580
Related