Early warning for when unsupported node versions stop working?

[ljharb]

Howdy!

I'm aware of the current support policy for npm; so for example, when v5.4 was released, it broke npm < v4.5 and < v5.10.

This is fine - and I built nvm install-latest-npm to make it easy in travis-ci (or elsewhere) to be able to get the latest working npm in your node version, whichever it is.

However, it'd be super super helpful if, in advance of a next being promoted to latest, the minor versions of node that worked on the previous release and no longer work on this release could be at least known, so I can add them to nvm.sh, and publish it, so it's available on travis-ci builds prior to next getting promoted to latest.

Is there any way your travis-ci builds for CLI could include extra minors as allowed failures, or something similar? I'm open to suggestions, and it'd be nice if "a non-npm person maintaining a travis-ci run that alerts on new failures" wasn't the only option available.

[ljharb]

I was pointed to

npm/lib/utils/unsupported.js

Line 9 in fb28e58

var knownBroken = '<4.7.0'

by @iarna on twitter, which is helpful.

What would be ideal is a text-only .tab file somewhere, with a mapping of npm version to "lowest supported node version" - then i could adapt nvm to read this file instead of having to hardcode all the logic.