Version Management not very clear.

[ExchangeEffect]

I using windows 10 version 1511 OS build 10586.318.. When I do node -v I get v4.4.5 as a response and when i do npm -v I get 2.15.5.
Problem one is labeling version is not consistent one has v displayed other there is no v displayed. There is no consistency on how the version command displays results.
Problem two is the documentation on https://nodejs.org/en/download/releases/ introduces latency in the implementation of nodejs in a production run. What I mean is it introduces the io.js, do we really need another name for nodejs ? .IF Forked happen.. as stated by the video
https://www.youtube.com/watch?v=JPMGA-94apc
FINE but when nodejs documentation mentions io.js inside nodejs documentation. It feels like opening a Ford car manual and finding instructions that mention Toyota.

[jasnell]

npm is a separate project managed by a different team with their own standards regarding how version numbers are displayed. I would direct questions regarding how their versions are printed to their repo (https://github.com/npm/npm). Printing the v prefix is standard for Node.js and likely will not be changing.

The io.js versions are all considered to be proper Node.js releases and are therefore listed in the releases page.