Package Exports

@pkgjs/nv

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@pkgjs/nv) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Get information about Node.js versions

Usage

$ npm i @pkgjs/nv

const nv = require('@pkgjs/nv')

(async () => {
  const versions = await nv('lts')
  console.log(versions)
  /*
[
  {
    version: '10.16.3',
    major: 10,
    minor: 16,
    patch: 3,
    codename: 'dubnium',
    versionName: 'v10',
    start: 2018-04-24T00:00:00.000Z,
    lts: 2018-10-30T00:00:00.000Z,
    maintenance: 2020-04-01T00:00:00.000Z,
    end: 2021-04-01T00:00:00.000Z
  }
]
  */
})()

You can also pass an array of aliases and the resulting array will be sorted and de-duped, for example:

const versions = await nv(['lts', 'maintained'])
console.log(versions.map((v) => v.version))
/*
[ '8.16.1', '10.16.3', '12.11.0' ]
*/

Supported Aliases

Support Aliases

For now referenced here until we have a more official doc: https://github.com/nodejs/package-maintenance/issues/236#issue-474783582

all: All node versions
lts_active: Head of LTS and Active major version lines
lts: Head of current LTS lines
active: The newest version in the active but not maintenence mode lines
lts_latest/lts/*: Latest of the LTS lines (lts/* for nvm compat)
maintained: Head of all maintained lines
current: Newest of all maintained lines

Version Aliases

v6, v8, v10, v12, etc: Head of major version line by version number
dubnium, carbon: Named alias for LTS lines