Bug report

The webpack inner semver function computed result is different from the npm package semver , and the webpack inner function result seems not right.

What is the current behavior?

Running the function satisfy from semver and parseRange results in a possible bug. Specifically:

satisfy(parseRange('~1'), '1.2.3') === false

What is the expected behavior?

satisfy(parseRange('~1'), '1.2.3') === true

Other relevant information:
the result is not the same with semver

const semver = require('semver');
semver.satisfies('1.2.3','~1') === true