doc: indicate the format of process.version

[dguo]

I needed to parse process.version and didn't know that it is prefixed with a v until I inspected the value.

As an aside, it seems inconsistent to me that process.version is prefixed with a v, but process.versions.node isn't. Would it be worth opening an issue to discuss that?

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• documentation is changed or added
• commit message follows commit guidelines

[Trott]

As an aside, it seems inconsistent to me that process.version is prefixed with a v, but process.versions.node isn't. Would it be worth opening an issue to discuss that?

I'd need to check, but I think that was intentional. process.version preceded process.versions and using the 'v' seemed like a mistake because almost nobody ever needs it and has to strip it out to deal with the version as a number. But changing process.version would cause too much ecosystem breakage.

[Trott]

I'd need to check, but I think that was intentional. process.version preceded process.versions and using the 'v' seemed like a mistake because almost nobody ever needs it and has to strip it out to deal with the version as a number. But changing process.version would cause too much ecosystem breakage.

If my recollection is correct, it may be worthwhile to have a discussion about documentation-deprecating process.version to point people at process.versions.node instead.

[Trott]

If my recollection is correct, it may be worthwhile to have a discussion about documentation-deprecating process.version to point people at process.versions.node instead.

Or that conversation might be made unnecessary by the change here. Maybe it's enough to direct people to the right thing.

[Trott]

Landed in 0dae5d9