`npm global latest` not properly applied

[c-vetter]

Despite having installed npm 5, I get npm 4 for latest, as can be seen from this shell excerpt:

$ nodist npm + latest
https://codeload.github.com/npm/npm/tar.gz/v5.0.4 [===========    ] 3447/4599 KiB 75% 23.8s

$ nodist npm
> 4.0.5  (global: 4.0.5)
  5.0.4

$ nodist npm global latest
npm latest

$ nodist npm
> 4.0.5  (global: latest)
  5.0.4

$ nodist npm global 5
npm 5

$ nodist npm
  4.0.5
> 5.0.4  (global: 5)

[Adam Bosco]

I too have run into this issue - it almost appears that nodist selects the oldest version of NPM available instead of the most recent, despite downloading the latter:

$ nodist npm
> 2.15.12  (global: latest)
  3.10.10
  4.0.5
  4.4.4
  5.1.0
  5.3.0

$ nodist npm global latest
npm latest
https://codeload.github.com/npm/npm/tar.gz/v5.4.2 [===========    ] 3762/5016 KiB 75% 2.0s

$ nodist npm
> 2.15.12  (global: latest)
  3.10.10
  4.0.5
  4.4.4
  5.1.0
  5.3.0
  5.4.2

$ nodist npm global 5
npm 5

$ nodist npm
  2.15.12
  3.10.10
  4.0.5
  4.4.4
  5.1.0
  5.3.0
> 5.4.2  (global: 5)

[Ben Burns]

I've found that the latest alias isn't working anywhere in nodist to update the version of node or NPM running. You can use it to download and install a new version, but if you want to actually use that version you need to reference it by its version number.

[Sebastian Große]

Seems to work as expected in new release v.10.3