npm-check picks an update from a deprecated version
Opened this issue · 3 comments
Steps to reproduce:
$ npm install --global elm
+ elm@0.19.0-bugfix2
$ npm-check --global
The global path you are searching is: /usr/local/lib/node_modules
elm 😎 MAJOR UP Major update available. https://github.com/elm/compiler/tree/master/installers/npm
npm install --global elm@2.0.0 to go from 0.19.0-bugfix2 to 2.0.0
2.0.0 is the highest version number indeed, however, it was deprecated a while ago after switching to a newer versioning system: https://www.npmjs.com/package/elm?activeTab=versions
(check show deprecated versions)
I know this is an edge case, but it'd be still great if npm-check was only picking the latest version amongst non-deprecated ones. 🙌 Otherwise it takes a few minutes to figure out what's wrong, which was the case for me this morning.
Neat package folks 💯
Ran into the same issue. Would be nice if npm-check ignores deprecated versions.
When the latest version is deprecated, it might also mean that the entire package is deprecated in favor of a different package. For instance, package cuid is deprecated at the moment and the right path to upgrade is to switch to a different package altogether. I feel like it’s in the spirit of the npm-check design goals.