4 ms·
that's surprisingly dumb, isn't it? semver.satisfies('7.0.0-rc1', '>=6.0.0') false
by kevinastone 10y ago
that's surprisingly dumb, isn't it?
semver.satisfies('7.0.0-rc1', '>=6.0.0')
false
- nilliams 10y agoNot really, you get a warning that said module might not support this 'release candidate' of a major breaking version.
- geofft 10y agoWeird. https://docs.npmjs.com/misc/semver#prerelease-tags https://docs.npmjs.com/misc/semver#prerelease-tags I guess the argument is that, if you're going to use ">=6.0.0" to choose a version of node.js, and your options are 6.1.0 and 7.0.0-rc1, you don't want a random release candidate. But if you're going to use it to verify an existing version of node.js, a 7.0.0-rc1 that someone else chose should be considered acceptable. Their semver rules can't distinguish these two cases. PEP 440 seems to handle this by decoupling the prerelease rules and the version-comparison rules: https://www.python.org/dev/peps/pep-0440/#handling-of-pre-releases https://www.python.org/dev/peps/pep-0440/#handling-of-pre-re... "Pre-releases of any kind, including developmental releases, are implicitly excluded from all version specifiers, unless they are already present on the system, explicitly requested by the user, or if the only available version that satisfies the version specifier is a pre-release."
- Touche 10y agoMajor releases are potentially breaking