npm / node-semver

100%

master: 100%

LAST BUILD ON BRANCH isaacs/range-subset-with-stars-and-prereleases

branch: isaacs/range-subset-with-stars-and-prereleases

CHANGE BRANCH

x

Reset

• isaacs/range-subset-with-stars-and-prereleases
• GH-164
• PR-316
• add-coerce-capability
• dont-publish-test
• exciting-travis-stuff
• fix-comment-divergence
• isaacs/optimization-reduce-unnecessary-comparators-in-range-set
• isaacs/remove-lazy-require
• isaacs/subset
• isaacs/tree-shaking-pr-295-continued
• master
• maxb/fix-range-intersects
• v4.3.5
• v4.3.6
• v5.0.0
• v5.0.1
• v5.0.2
• v5.0.3
• v5.1.0
• v5.1.1
• v5.2.0
• v5.3.0
• v5.4.0
• v5.4.1
• v5.5.1
• v5.6.0
• v6.1.0
• v6.1.1
• v6.1.2
• v6.1.3
• v6.2.0
• v6.3.0
• v7.0.0
• v7.1.0
• v7.1.1
• v7.1.2
• v7.1.3
• v7.2.0
• v7.2.1
• v7.2.2
• v7.2.3
• v7.3.0
• v7.3.1
• v7.3.2
• v7.3.3
• v7.3.4
• v7.3.5

Build # 340

Build Type

push

travis-ci

Committed by isaacs

Commit Message

Correctly handle prereleases/ANY ranges in subset

An "ANY" range (ie, `""`, `*`, etc.) does not include prerelease
versions except when `includePrerelease` flag is set.

Also, merely looking at the max/min boundaries of any ranges ignores the
fact that the sub range maybe including prerelease versions that are
excluded from the super range.  For example, `>=1.2.3-pre.0` is _not_ a
subset of `>=1.0.0`, because it inludes `1.2.3-pre.0`, `1.2.3-pre.1`,
and so on.

PR-URL: https://github.com/npm/node-semver/pull/377
Credit: @isaacs
Close: #377
Reviewed-by: @wraithgar

Run Details

766 of 766 branches covered (100.0%)

1059 of 1059 relevant lines covered (100.0%)

234.03 hits per line