By default, the semver library excludes prerelease check unless explicitly included in the range: https://github.com/npm/node-semver#prerelease-tags. This behavior is handy for the wide range of npm packages where their authors can publish any versions breaking SemVer rules and those version will be picked up by ranges specified by users and installed breaking application. For the purpose of this plugin, we only deal with two mature projects and check that version matches the range specified by the user, but never install/update this version. If the user chose the >X.Y.Z constraint, we assume that they know what they are doing and choose less surprising SemVer range checking behavior.
By default, the
semverlibrary excludes prerelease check unless explicitly included in the range: https://github.com/npm/node-semver#prerelease-tags. This behavior is handy for the wide range of npm packages where their authors can publish any versions breaking SemVer rules and those version will be picked up by ranges specified by users and installed breaking application. For the purpose of this plugin, we only deal with two mature projects and check that version matches the range specified by the user, but never install/update this version. If the user chose the>X.Y.Zconstraint, we assume that they know what they are doing and choose less surprising SemVer range checking behavior.Fixes #10