"npm install node@lts" reports 12.18.1 which does not match 12.18.2 listed on website about node-bin-gen HOT 7 CLOSED

Thanks! Fixed!

In general, I maintain vX-lts tags, since multiple branches can be lts at once, and tagging just 'lts' means you might get a major version without warning. That said lts should be maintained and is now pointing to 12.18.2.

from node-bin-gen.

There's a json file on nodejs.org in the downloads directory that could be used for automation

from node-bin-gen.

The json file is at https://nodejs.org/dist/index.json

from node-bin-gen.

...if there is a better way to programmatically pull the LTS version I am definitely all ears. I just assumed this was part of the build and deploy process for NodeJS / NPM :) Thanks for the fix.

from node-bin-gen.

Heh, it's actually kinda manual on my part. I keep meaning to script it but never get around to it.

you can use the tag v12-lts if you want to pin to 12. Your case ("we want to test against whatever LTS is declared to be") might be the good reason to use the lts tag tho

from node-bin-gen.

Hmmm, I could not find that json file linked or in the source code for the page. My team also uses nvm to manage the node version switching and it looks like nvm has this command which could work well for us depending on how often nvm keeps it up to date:

nvm version-remote --lts

Found it here: nvm-sh/nvm#1706

from node-bin-gen.

And yeah, it's super hidden unless you directory hack your way there and realize that nodejs has old school FTP-site style parts.

from node-bin-gen.