e.g.
``` sh
npm info gaze
{ name: 'gaze',
description: 'A globbing fs.watch wrapper built from the best parts of other fine watch libs.',
'dist-tags': { latest: '0.5.2' },
versions:
// ..
'0.4.2',
'0.4.3',
'0.5.0',
'0.5.1',
'0.5.2',
'0.6.0',
'0.6.1',
'0.6.2',
'0.6.3',
'0.6.4' ],
maintainers: [ 'joshperry <[email protected]>', 'shama <[email protected]>' ],
time:
{ modified: '2015-10-05T20:28:06.595Z',
created: '2012-10-04T17:46:14.249Z',
// ..
'0.6.1': '2014-04-14T05:31:53.674Z',
'0.6.2': '2014-04-14T18:31:18.128Z',
'0.6.3': '2014-04-15T03:03:33.464Z',
'0.6.4': '2014-04-21T18:40:11.152Z',
'0.5.2': '2015-10-05T20:28:06.595Z' },
// ..
```
Notice that the greatest version is `0.6.4` but the latest version is `0.5.2`. `salita` wrongly picks up the latest, not the greatest version.
This is intentional - when a version is larger but not tagged "latest", it's likely a beta, or has other caveats, and shouldn't be blindly updated to.
However, when the version already in your package.json is already higher than the "latest", I agree that `salita` should update it to the greatest available. Is that the case here?
If the current version is `0.6.3` then running `salita` gives:
```
salita
Found package.json.
Dependencies:
Requested range not satisfied by: gaze from ^0.6.3 to ^0.5.2
Development Dependencies:
None found
0 updated out of 1 total dependencies.
```
which neither updates it to `0.6.4` or `0.5.2`.
This is a problem with gaze. They have not yet updated their latest stable. It is currently set at 0.5.2, even though the most recent version is 0.6.4. Maybe they consider this version unstable? I can only speculate, but it's definitely a problem with that package and not how Salita is intended to work.
I do think there's validity in, if a package.json contains a version that is already greater than the "latest" (but is not a prerelease), that `salita` could update to the latest version (in semver terms) in `npm show`.
However, that's a very edge case, so I don't consider it a high priority.